JDK-6441763 : RFE:Class Data sharing archive should support as many jar files as possible from bootclasspath
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2006-06-21
  • Updated: 2014-06-25
  • Resolved: 2014-06-25
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.
Related Reports
Duplicate :  
Currently the maximum number of jar files we can put in the bootclasspath (bcp) in order to generate class data sharing archive is 8, with fix of JDK-6304817, it will be changed to 32. This is still not flexible. One of the problem is if ISVs put more than 30 jar files in the jre/lib/endorsed directory, the problem mentioned in JDK-6440118 will still appear. The ultimate way to solve the issue is to allow as many jar files as possible from bcp. Since it involves a good amount of changes if we make a varible length header of class data sharing archive, I think it would make sense to do it in dolphin.

Closed as a duplicated of JDK-8046070

Part of JDK-8046070 changes will remove the hard limit of the number of JAR files in the CDS archive.

EVALUATION Commit it to dolphin.