JDK-6539723 : Class Data Sharing cease to work on Windows on Daylight Saving time change
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2007-03-28
  • Updated: 2012-10-08
  • Resolved: 2007-06-20
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 6 JDK 7 Other
6u4Fixed 7Fixed hs10Fixed
Description
FULL PRODUCT VERSION :
Java(TM) SE Runtime Environment (build 1.6.0_01-ea-b03)
Java HotSpot(TM) Client VM (build 1.6.0_01-ea-b03, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]

A DESCRIPTION OF THE PROBLEM :
Since the CDS feature was introduced in 5.0 it always ceases to work 2-times a year just immediately after Daylight saving change takes place. To make it work again one have to "dump" the shared archive file again.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
1) install jre or jdk on windows
2) verify that java.exe -Xshare:on works
3) wait for start of end of daylight saving time change
4) see that java.exe -Xshare:on fails

ERROR MESSAGES/STACK TRACES THAT OCCUR :
An error has occured while processing the shared archive file.
A jar file is not the one used while building the shared archive file.
Error occurred during initialization of VM
Unable to use shared archive.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Rebuild the shared archive file twice a year manually is NOT an option for JOE the user rendering CDS useless.

Comments
EVALUATION Windows 'last modified' times can be modified in some cases by the daylight savings time adjustment. This is likely what is going on here. A possible workaround: http://support.microsoft.com/default.aspx?scid=kb;en-us;190315
24-05-2007