IV82849: HANG DUE TO JIT COMPILATION THREAD OMITTING TO SEND A NOTIFICATION SIGNAL WHEN COMPILATION ENDS

APAR status

• Closed as program error.

Error description

• 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)
  

Local fix

Problem summary

• 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.
  

Problem conclusion

• 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       (8.0.3.0)
     7 R1 SR3 FP40  (7.1.3.40)
     7    SR9 FP40  (7.0.9.40)
     6 R1 SR8 FP25  (6.1.8.25)
  .
  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/
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  JIT

• Fixed component ID

  620700124

Applicable component levels

• R130 PSY

     UP

• R260 PSY

     UP