IV69509: HANG IN JAVA.UTIL.CONCURRENT.LOCKS.ABSTRACTQUEUEDSYNCHRONIZER.CONDITIONOBJECT.AWAITNANOS
A fix is available
Closed as program error.
Error Message: The JVM becomes unresponsive with low (but nonzero) CPU usage. . Stack Trace: 3XMTHREADINFO3 Java callstack:4XESTACKTRACE at sun/misc/Unsafe.park(Native Method)4XESTACKTRACE at java/util/concurrent/locks/LockSupport.parkNanos(LockSupport.jav a:226)4XESTACKTRACE at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionO bject.awaitNanos(AbstractQueuedSynchronizer.java:2089(Compiled Code))Note that ConditionObject.awaitNanos is listed as "Compiled Code". . Only occurs on the Linux ia32 platform, and only with -Xshareclasses. Another symptom of the same problem is that System.nanoTime can return an answer 1000x smaller than expected.
AOT-compiled methods calling System.nanoTime could use a flawed algorithm that produced a result that is 1000x too small. As a result, ConditionObject.awaitNanos would wait for 1000x longer than requested.
The JIT has been modified to call the correct nanoTime implementation. . This APAR will be fixed in the following Java Releases: 8 SR1 (184.108.40.206) 6 R1 SR8 FP4 (220.127.116.11) 6 SR16 FP4 (18.104.22.168) 7 R1 SR3 (22.214.171.124) 7 SR9 (126.96.36.199) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, information about the Service Refreshes and Fix Packs can be found at: https://www.ibm.com/developerworks/java/jdk/
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID