IV65396: JDMPVIEW FAILS TO IDENTIFY CRASHING THREAD IN A ZOS CORE DUMP

APAR status

• Closed as program error.

Error description

• Error Message: jdmpview -core
  PMR67024.082.000.MQTTBRK.JUL15.T095050DTFJView version 4.27.73,
  using DTFJ version 1.11.27025Loading image from DTFJ......*5 :
  ASID: 0xcb EDB: 0x48001055e8 : JRE 1.7.0 z/OS s390x-64 build
  20130422_146026 (pmz6470sr4fp2-20130426_01(SR4 FP2) )6 : ASID:
  0xffff : No JRE : No JREinfo threadnative threads for address
  spaceprocess id: 34079553no native threads found with specified
  id
  .
  Stack Trace: N/A
  .
  The zOS core dump was externally triggered via the zOS console,
  not by the JVM.
  

Local fix

• Use the jdmpview 'info thread *' or 'info thread all' command to
  list all threads, then examine the thread stacks and thread
  properties to find the crashing thread.
  

Problem summary

• The DTFJ API used by the jdmpview tool was relying on JVM data
  to identify the crashing thread. For dumps triggered externally
  it needs to use native thread data instead.
  

Problem conclusion

• The DTFJ API used by the jdmpview tool has been updated to  use
  native thread data to identify the crashing thread in cases
  where the dump was triggered externally.
  .
  This APAR will be fixed in the following Java Releases:
     7 R1 SR2       (7.1.2.0)
     7    SR8       (7.0.8.0)
     6 R1 SR8 FP2   (6.1.8.2)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, Java maintenance is available
  from:
             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

• R260 PSY

     UP