IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Using Javadump

Triggering a Javadump

Javadumps can be triggered by error conditions, or can be initiated in a number of ways to obtain diagnostic information.

Javadumps triggered by error conditions

By default, a Javadump is triggered when one of the following error conditions occurs:

A fatal native exception

Not a Java™ Exception. A "fatal" exception is one that causes the JVM to stop. The JVM handles the event by producing a system dump followed by a snap trace file, a Javadump, and then terminating the process.

The JVM has insufficient memory to continue operation

There are many reasons for running out of memory. See Problem determination for more information.

Javadumps triggered by request

You can initiate a Javadump to obtain diagnostic information in one of the following ways:

You can send a signal to the JVM from the command line

On Windows systems, use the keyboard combination CTRL+Break in the command window that started Java to trigger the Javadump.

The JVM continues after the signal has been handled.

You can use the JavaDump() method in your application

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 continues after the Javadump is produced.

You can initiate a Javadump using the wasadmin utility

In a WebSphere Application Server environment, use the wasadmin utility to initiate a dump.

The JVM continues after the Javadump is produced.

You can configure a dump agent to trigger a Javadump

Use the -Xdump:java: option to configure a dump agent on the command line. See Using the -Xdump option for more information.

You can use the trigger trace option to generate a Javadump

Use the -Xtrace:trigger option to produce a Javadump by calling the substring method shown in the following example:

-Xtrace:trigger=method{java/lang/String.substring,javadump}

For a detailed description of this trace option, see trigger=<clause>[,<clause>][,<clause>]...

Parent: Using Javadump

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.