IV82849: HANG DUE TO JIT COMPILATION THREAD OMITTING TO SEND A NOTIFICATI ON SIGNAL WHEN COMPILATION ENDS
Closed as program error.
Error Message: N/A . Stack Trace: N/A . A javacore for the hung process will show an application thread waiting to be notified on a JIT-QueueSlotMonitor. E.g.: 2LKREGMON JIT-QueueSlotMonitor-1353 lock (0x00007F4058189C80): <unowned> 3LKNOTIFYQ Waiting to be notified: 3LKWAITNOTIFY "Pooled Thread #71 running gnu.testlet.java.util.AbstractMap.AcuniaAbstractMapTest" (J9VMThread:0x00007F4200311400)
Under some circumstances an application thread may request a synchronous re-compilation to be performed and thus, the thread is going to wait for the compilation to finish before continuing. In some rare cases the JIT compilation thread may omit to send a notification when the compilation is over resulting in the waiting thread being blocked forever.
The code has been changed to send the notification signal to the waiting thread. . This APAR will be fixed in the following Java Releases: 8 SR3 (188.8.131.52) 7 R1 SR3 FP40 (184.108.40.206) 7 SR9 FP40 (220.127.116.11) 6 R1 SR8 FP25 (18.104.22.168) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, information about the available 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
Applicable component levels