JDK-6924920 : Class Data Sharing limit on the java version string can create failures: JVM Ident field too long
  • Type: Bug
  • Status: Closed
  • Resolution: Fixed
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P3
  • Affected Version: 7
  • OS: generic
  • CPU: generic
  • Submit Date: 2010-02-10
  • Updated Date: 2014-06-26
  • Resolved Date: 2012-11-28
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 Availabitlity Release.

To download the current JDK release, click here.
JDK 8 Other
8Fixed hs25Fixed
Description
If the java -client -Xinternalversion string exceeds 256, running java -client -Xshare:dump will fail:


>>>> VM option 'SharedReadOnlySize=10M'
>>>> Rewriting and unlinking classes ... done.
>>>> Calculating hash values for String objects .. done.
>>>> Calculating fingerprints ... done.
>>>> Removing unshareable information ... done.
>>>> Moving pre-ordered read-only objects to shared space at 0x3c010000 ... done.
>>>> Moving read-only objects to shared space at 0x3c5285e0 ... done.
>>>> Moving common symbols to shared space at 0x3c52a638 ... done.
>>>> Moving remaining symbols to shared space at 0x3c5e3248 ... done.
>>>> Moving string char arrays to shared space at 0x3c5e44a8 ... done.
>>>> Moving additional symbols to shared space at 0x3c666118 ... done.
>>>> Read-only space ends at 0x3c6f9ef0, 7249648 bytes.
>>>> Moving pre-ordered read-write objects to shared space at 0x3ca10000 ... done.
>>>> Moving read-write objects to shared space at 0x3d039110 ... done.
>>>> Moving String objects to shared space at 0x3d0711e0 ... done.
>>>> Read-write space ends at 0x3d0ae668, 6940264 bytes.
>>>> Updating references to shared objects ... done.
>>>>
>>>> Error occurred during initialization of VM
>>>> Unable to use shared archive.
>>>> ",stderr="An error has occurred while processing the shared archivefile.
>>>> JVM Ident field for shared archive is too long - truncated to
>>>> <????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
??!
>>>> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????j>


I would like to see this 256 limit removed, increased, or truncate the version string silently. But please don't fail like this.