Java diagnostic tools

Links are provided in the online information on Java™ diagnostic tools.

Links are provided in the online information on Java diagnostic tools. For additional Information on Java diagnosis, see: IBM® Diagnosis documentation.

Java diagnostic output

When starting CICS® Transaction Gateway on Windows, any standard output or error text produced is captured in the file jvmdbg.log, located in the <product_data_path> directory. The purpose of this file is to capture debug output from the jvm, when the CICS Transaction Gateway is started with debug java startup parameters specified. For example:
ctgservice -R -A-j-verbose:init

JVM dump and system dump

JVM dumps and system dumps provide detailed information about the internal status of an IBM JVM, and the configuration of a running CICS Transaction Gateway.

JVM dumps provide a snapshot of a Java Runtime Environment (JRE). System dumps provide a snapshot of the JRE at a process level and also provide diagnostic information regarding the system status and configuration.

For more information, see Dumping diagnostic information.

With some Java Virtual Machines (JVMs) on UNIX and Linux you can force Java to write a stack dump showing the states of the current threads.

For example, on IBM JVMs, you can send a SIGQUIT (-3) signal to a Java process to make it write a stack dump to stderr. This shows the states of the current threads. Do not do this on a working production system but only on a system which is completely locked.


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/javadiagtools.html