Javadumps are triggered by a number of events, both in error situations and user-initiated.
By default, a Javadump is triggered when one of the following error conditions occurs:
You can also initiate a Javadump to obtain diagnostic information in one of the following ways:
The signal for AIX® is SIGQUIT. Use the command kill -QUIT n to send the signal to a process with process id (PID) n. Alternatively, press CTRL+\ in the shell window that started Java.
The JVM will continue operation after the signal has been handled.
The com.ibm.jvm.Dump class contains a static JavaDump() method that causes Java code to initiate a Javadump. In your application code, add a call to com.ibm.jvm.Dump.JavaDump(). This call is subject to the same Javadump environment variables that are described in Enabling a Javadump.
The JVM will continue operation after the JavaDump has been produced.
In a WebSphere® Application Server environment, use the wasadmin utility to initiate a dump.
The JVM will continue operation after the JavaDump has been produced.
-Xtrace:trigger=method{java/lang/String.substring,javadump}For a detailed description of this trace option, see trigger=<clause>[,<clause>][,<clause>]...