IV29820: MEMORY ANALYZER HANGS WHEN READING A 24 VM SYSTEM CORE

APAR status

• Closed as program error.

Error description

• Error Message: com.ibm.dtfj.image.CorruptDataException:
  J9DDRCorruptData <OSB>as=xcoff : 0 Message: Memory Fault reading
  0x06429E22 Address: 0x6429e22<CSB>
  .
  Stack Trace: at
  org.eclipse.mat.dtfj.DTFJIndexBuilder.logCorruptData(DTFJIndexBu
  ilder.java:4833)
                 at
  org.eclipse.mat.dtfj.DTFJIndexBuilder.isCorruptData(DTFJIndexBui
  lder.java:4572)
                 at
  org.eclipse.mat.dtfj.DTFJIndexBuilder.fill(DTFJIndexBuilder.java
  :1128)
                 at
  org.eclipse.mat.parser.internal.SnapshotFactoryImpl.parse(Snapsh
  otFactoryImpl.java:234)
                 at
  org.eclipse.mat.parser.internal.SnapshotFactoryImpl.openSnapshot
  (SnapshotFactoryImpl.java:138)
                 at
  org.eclipse.mat.snapshot.SnapshotFactory.openSnapshot(SnapshotFa
  ctory.java:145)
                 at
  org.eclipse.mat.ui.snapshot.ParseHeapDumpJob.run(ParseHeapDumpJo
  b.java:81)
                 at
  org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)??
  .
  Seen when running jdmpview or Memory Analyser on a core dump
  from a 2.4 J9 JVM.
  

Local fix

Problem summary

• The DTFJ API was not handling Java heap structures which were in
  flight when the core was produced.
  

Problem conclusion

• This defect will be fixed in:
  6.0.1 SR4
  7.0.0 SR3
  6.0.0 SR12
  .
  DTFJ heap walker has been updated to handle this situation.
  

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

• R260 PSY

     UP