Information Gathering › Run the Logging Script › Debug CA Chorus Application Server Problems › JVM Dumps

JVM Dumps

The CA Chorus Application Server may generate dumps for the following situations:

• When a program check in the native code ("gpf") encounters.
• When a system event, such as an Out Of Memory condition, occurs.

You see messages on the JESMSGLG output that look like the following messages:

10.55.59 STC48819 BPXM023I (CHORADM2) 547
547 JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" - please wait.
10.55.59 STC48819 BPXM023I (CHORADM2) 548
548 JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" - please wait.

In this case, there are two sets of files that get written to the file system for the server:

• javacore.yyyymmdd.hhmmss.pid.seq.txt—A human-readable text file (medium size, around 3 MB).
• heapdump.yyyymmdd.hhmmss.pid.seq.phd—A binary file (large size, around 255 MB).