IV72268: THE JVM MAY DEADLOCK DURING THE GENERATION OF DIAGNOSTIC FILES A S A CONSEQUENCE OF A CRASH

APAR status

• Closed as program error.

Error description

• Error Message: N/A
  .
  Stack Trace: N/A
  .
  Attaching the debugger to the hung JVM may show a native stack
  trace like the following:...........#4 0x00007f4ee33f2535 in
  recompileMethodForLog () from
  /jvm/jre/lib/amd64/default/libj9jit28.so#5 0x00007f4ee33f7ff5 in
  dumpJitInfo () from /jvm/jre/lib/amd64/default/libj9jit28.so#6
  0x00007f4ee8466529 in doJitDump () from
  /jvm/jre/lib/amd64/default/libj9dmp28.so#7 0x00007f4ee8465275 in
  protectedDumpFunction () from
  /jvm/jre/lib/amd64/default/libj9dmp28.so#8 0x00007f4ee8bf3e45 in
  j9sig_protect () from /jvm/jre/lib/amd64/default/libj9prt28.so#9
  0x00007f4ee8465239 in runDumpFunction () from
  /jvm/jre/lib/amd64/default/libj9dmp28.so..........
  

Local fix

Problem summary

• When the JVM experiences a crash it will attempt to create a set
  of diagnostics files to aid in debugging the problem. One such
  file is a JIT compilation log for the jitted body in which the
  crash occurred (if applicable). In some rare cases this activity
  can lead to a deadlock.
  

Problem conclusion

• The JIT has been modified to eliminate the deadlock condition.
  .
  This APAR will be fixed in the following Java Releases:
     7 R1 SR3       (7.1.3.0)
  .
  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