Failure to handle a Java exception

If an application or CICS Transaction Gateway fails to handle a Java exception, the Java™ Virtual Machine (JVM) writes a Java stack dump. This applies to Java exceptions in general.

Symptom

The JVM has written a Java stack dump.

Probable cause

An application or CICS Transaction Gateway failed to handle an exception.

Action

The destination for the dump output depends on your JVM implementation; check your Java documentation for more information.

To increase the information written to the Java stack dump, disable the Just-In-Time (JIT) compiler. The information included in the dump might include the line of Java source code where the exception happened. How you disable the JIT compiler depends on your JVM implementation; check your Java documentation for more information.

The following example shows a Java stack dump that was created with the JIT compiler disabled:

Exception in thread "main" java.lang.OutOfMemoryError
        at java.lang.Thread.start(Native Method)
        at com.ibm.ctg.server.ThreadManager.createObject
           (ThreadManager.java:345)
        at com.ibm.ctg.server.ThreadManager.<init>(ThreadManager.java:131)
        at com.ibm.ctg.server.ManagedResources.<init>
           (ManagedResources.java:106)
        at  com.ibm.ctg.server.JGate.main(JGate.java:895)

If the CICS Transaction Gateway handles an exception, a Java stack dump is written only if tracing is enabled. Try to reproduce the problem with tracing enabled because it helps to show you what was happening before the exception occurred. For more information, see Tracing.


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//ctgzos/zosjavaexceptions.html