You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/07/03 18:16:20 UTC

[jira] [Created] (SLING-2943) Classloader might not be invalidated in a cluster

Carsten Ziegeler created SLING-2943:
---------------------------------------

             Summary: Classloader might not be invalidated in a cluster
                 Key: SLING-2943
                 URL: https://issues.apache.org/jira/browse/SLING-2943
             Project: Sling
          Issue Type: Bug
          Components: JCR
    Affects Versions: JCR Classloader 3.1.12
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: JCR ClassLoader 3.1.14


The jcr classloader is invalided based on the fact if a previous class file can be deleted (through the class loader writer).
In a clustered installation, usually only the first instance receiving the changed event for a jsp is able to remove the class file; the other instances can't delete it, as it is already gone

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira