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 2010/01/20 17:50:55 UTC
[jira] Created: (SLING-1302) After a NoClassDefError classes are
still not found even if they have been installed in the meantime
After a NoClassDefError classes are still not found even if they have been installed in the meantime
----------------------------------------------------------------------------------------------------
Key: SLING-1302
URL: https://issues.apache.org/jira/browse/SLING-1302
Project: Sling
Issue Type: Bug
Components: Scripting
Reporter: Carsten Ziegeler
Use case:
A jsp uses a class from Bundle A - the first time this jsp is used Bundle A is available.
Bundle A is then uninstalled
Requesting the JSP results in a NoClassDefError as the class from Bundle A is not available anymore (this is expected!)
Installing Bundle A brings the required class back into the system
However the NoClassDefError does not get away
Restarting the jsp scripting solves the problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1302) After a NoClassDefError classes are
still not found even if they have been installed in the meantime
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1302.
-----------------------------------
> After a NoClassDefError classes are still not found even if they have been installed in the meantime
> ----------------------------------------------------------------------------------------------------
>
> Key: SLING-1302
> URL: https://issues.apache.org/jira/browse/SLING-1302
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons ClassLoader 1.1.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons ClassLoader 1.1.4
>
>
> Use case:
> A jsp uses a class from Bundle A - the first time this jsp is used Bundle A is available.
> Bundle A is then uninstalled
> Requesting the JSP results in a NoClassDefError as the class from Bundle A is not available anymore (this is expected!)
> Installing Bundle A brings the required class back into the system
> However the NoClassDefError does not get away
> Restarting the jsp scripting solves the problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1302) After a NoClassDefError classes are
still not found even if they have been installed in the meantime
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1302:
------------------------------------
Component/s: (was: Scripting)
Commons
Affects Version/s: Commons ClassLoader 1.1.2
Fix Version/s: Commons ClassLoader 1.1.4
Assignee: Carsten Ziegeler
After some debugging I found the problem: the dynamic classloader - the package admin classloader uses a negativ cache: if a class
is not found, the class name is put into a cache for improved performance.
However, if a bundle is installed, this cache is not cleared.
Moving this bundle to the dynamic classloader.
> After a NoClassDefError classes are still not found even if they have been installed in the meantime
> ----------------------------------------------------------------------------------------------------
>
> Key: SLING-1302
> URL: https://issues.apache.org/jira/browse/SLING-1302
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons ClassLoader 1.1.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons ClassLoader 1.1.4
>
>
> Use case:
> A jsp uses a class from Bundle A - the first time this jsp is used Bundle A is available.
> Bundle A is then uninstalled
> Requesting the JSP results in a NoClassDefError as the class from Bundle A is not available anymore (this is expected!)
> Installing Bundle A brings the required class back into the system
> However the NoClassDefError does not get away
> Restarting the jsp scripting solves the problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1302) After a NoClassDefError classes are
still not found even if they have been installed in the meantime
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1302.
-------------------------------------
Resolution: Fixed
Clearing the negative caches now on bundle resolved events - fixed in revision 902807
> After a NoClassDefError classes are still not found even if they have been installed in the meantime
> ----------------------------------------------------------------------------------------------------
>
> Key: SLING-1302
> URL: https://issues.apache.org/jira/browse/SLING-1302
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons ClassLoader 1.1.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons ClassLoader 1.1.4
>
>
> Use case:
> A jsp uses a class from Bundle A - the first time this jsp is used Bundle A is available.
> Bundle A is then uninstalled
> Requesting the JSP results in a NoClassDefError as the class from Bundle A is not available anymore (this is expected!)
> Installing Bundle A brings the required class back into the system
> However the NoClassDefError does not get away
> Restarting the jsp scripting solves the problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.