DFHAP1300 DATE TIME APPLID The JVM at address X'jvm_anchor' on thread X'thread_anchor' has encountered an error (reason code: X'reason_code') and has requested further diagnostic data from CICS. More information may be found in the STDERR file: stderr.
Explanation
An error condition was detected by one of the JVMs in the JVMPool. The JVM invoked CICS services to capture a system dump. The JVM may recover, and continue processing, or may terminate. The JVM may write further data to the current stderr file indicated in the message.
System action
A system dump is taken. For critical errors in the JVM, the JVM is terminated. If a CICS program was in control at the time of the failure, the program is abended. If the failure occurred during task termination, the current transaction is rolled back. Processing continues by recreating the JVM or using other JVMs in the JVMPool.
User response
Read the STDERR log for the JVM. The JVM will have written any of its own diagnostics messages to this location. Examine the system dump using the JVM formatting utility. Use the address (jvm_anchor) shown in the message to identify the JVM. Optionally, use the address (thread_anchor) shown in the message to identify the thread in the JVM. The failure may be due to a JVM internal error, or to a component loaded by the JVM as a Native method or plug-in. The reason code given (reason_code) may be a signal handle or other code defined by the JVM. Use the information generated by the JVM in the stderr file to assist in the diagnosis of the problem.
Module
XMEOUT parameters/Message inserts
- DATE
- TIME
- APPLID
- X'jvm_anchor'
- X'thread_anchor'
- X'reason_code'
- stderr
Destination
CSMT