Bug ID: JDK-6474541 Thread.sleep different implementation in Solaris affected by time change

Type: Enhancement
Component: hotspot
Sub-Component: runtime
Affected Version: 1.4.2_12

Priority: P3
Status: Closed
Resolution: Cannot Reproduce
OS: solaris_9
CPU: generic

Submitted: 2006-09-25
Updated: 2015-04-06
Resolved: 2015-04-06

Versions (Unresolved/Resolved/Fixed)

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 9
9Resolved

Customer submitted a program that starts 2 threads and do a Thread.sleep at 10s and 60 seconds.  They observed that if time is changed during this interval, the thread that is supposed to sleep for 60 seconds wakes prematurely on Solaris sparc platform.

Based on Nicolay's comment, we don't think this is a problem in modern versions of Solaris. Closing as CNR.
06-04-2015
This would need detailed investigation to determine how/if the various "sleep" mechanisms are affected by system time changes. From other comments it can be seen that Solaris bugs have affected this so the original problem may no longer even exist in reasonably current S10 updates. Be wary of trying to experiment with this on a non-physical Solaris system - virtual environments add another level of complexity to the problem.
09-04-2013
We should evaluate how to fix this, and then evaluate the risk of the change - to determine what release to put this in
09-04-2013
EVALUATION -- deleted --- see comments
08-10-2008

Relates :	JDK-6546236 - Thread interrupt() of Thread.sleep() can be lost on Solaris due to race with signal handler
Relates :	JDK-6751923 - JNDI wake up when clock_settime() is called