IJ03413: HANG CREATING THREAD AFTER REDEFINING CLASSES

APAR status

• Closed as program error.

Error description

• Error Message: N/A
  .
  Stack Trace: Stack trace of hanging thread:
  #0  0x0000003aee40b68c in pthread_cond_wait@@GLIBC_2.3.2 () from
  /lib64/libpthread.so.0
  #1  0x00007f50d388a8e5 in monitor_wait_original () from
  /team/mli/ilog/sdk/jre/lib/amd64/compressedrefs/libj9thr29.so
  #2  0x00007f50d3b00fec in internalAcquireVMAccessNoMutexWithMask
  (vmThread=0x3181400, haltMask=40965) at VMAccess.cpp
  #3  0x00007f50d3b02019 in inlineAcquireVMAccessExhaustiveCheck
  (currentThread=0x3181400) at ../oti/VMAccess.hpp
  #4  internalAcquireVMAccess (currentThread=0x3181400) at
  VMAccess.cpp
  #5  0x00007f50d3b558ab in javaProtectedThreadProc
  (portLibrary=<value optimized out>, entryarg=0x3181400) at
  vmthread.c
  .
  

Local fix

• -XX:-OSRSafePoint will work around the issue, at the cost of
  runtime performance.
  

Problem summary

• There was a lock ordering issue in the JVM which affected
  threads being created during a class redefinition.
  

Problem conclusion

• The lock ordering has been corrected.
  .
  This APAR will be fixed in the following Java Releases:
     8    SR5 FP10  (8.0.5.10)
  .
  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

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R270 PSY

     UP