[SLING-1435] After a NoClassDefError classes are still not found even if they have been installed in the meantime with Java 6

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Commons ClassLoader 1.1.4
• Fix Version/s: Commons ClassLoader 1.2.0
• Component/s: Commons
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 10/Mar/10 14:57
• Updated: 20/Sep/17 13:02
• Resolved: 11/Mar/10 08:40

Description

Scenario - note that this works fine with Java 5, but on Java 6 we have:

• A jsp instanties a class from bundle A with the new operator
• JSP is loaded - everything is working fine
• Bundle A is uninstalled
• JSP invocation results in NoClassDefFoundError (which is expected)
• Bundle A is installed
• JSP is invoked and as soon as the new operator is called a NoClassDefFoundError is called

It seems that Java 6 behaves differently than Java 5: The jsp can be loaded and executed, but as soon as the class from Bundle A is used, Java 6 memorieses that the class was gone inbetween and it is not possible to update this state somehow. All involved classloaders are not queried anymore

Issue Links

• is related to: SLING-4806 Only invalidate those DynamicClassLoaderManagers which are becoming invalid