JDK-6304817 : The class data sharing archive does not work when jar file in bootclasspath is more than 8
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 5.0,6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-08-01
  • Updated: 2012-10-08
  • Resolved: 2006-07-11
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.
Other JDK 6
5.0u10Fixed 6 b91Fixed
Related Reports
Duplicate :  
JDK-6440118 - Shared archive not generated when jre/lib/endorsed contains more than one jar file
Description
The class data sharing archive currently only supports less or equal than 8 jar files in bootclasspath. I was trying to split rt.jar into various small jar files to better manager the classes in JDK and hope the shared archive working, but failed.

We should increase that number to 16 or more.
Comments
EVALUATION I filed a different bug (6441763: RFE:Class Data sharing archive should support as many jar files as possible from bootclasspath) to make the class data sharing archive to support as many jar files in bootclasspath as possible. The hardcoded solution mentioned in last evalution is a workaround for Mustang (and possibly for tiger update release).
21-06-2006
EVALUATION Change JVM_SHARED_JARS_MAX from 8 to 32 should solve the problem.
20-06-2006