JDK-7055240 : Mlet classloader is unable to load resource files in java se 6
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6u25,7
  • Priority: P2
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2011-06-15
  • Updated: 2014-11-19
  • Resolved: 2011-08-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Resolved
Description
SHORT SUMMARY:

MLET CLASSLOADER IS UNABLE TO LOAD RESOURCE FILES IN JAVA SE 6

INDICATORS:

MLet classloader is unable to load resource files that are contained in jar 
files.
The issue is reproducible in Java SE 6, and works fine in Java SE 5.0.

COUNTER INDICATORS:

works in jdk5

TRIGGERS:

jdk 6

KNOWN WORKAROUND:

See testcase. (will attach post shadow bug creation. On vacation till Mon 
20th Jun however)

PRESENT SINCE:

fcs

HOW TO VERIFY:

See testcase attached to bugdb (will attach to bugster shortly)

NOTES FOR SE:

None

REGRESSION:

Yes
Comments
WORK AROUND trivial workaround available: add jar files, that resources need to be obtained from, to the classpath
14-07-2011
EVALUATION Upon further investigation it seems that JAF is now part of the JDK. MailcapCommandMap's _class_loader is set to null in JDK 6 and javax.management.loading.MLet in JDK5 presumably as a result. That being the case, it seems we're trying to load the resources in the testcase with the bootstrap classloader which fails, where previously we were using MLet.
08-07-2011
EVALUATION After playing with the testcase it appears that there are differences in class loading in jdk5 vs 6 which seem to be responsible for this bug. I'm happy with the accepted state and will update when I know more.
06-07-2011