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

Using Javadump

Javadump produces files that contain diagnostic information related to the JVM and a Java™ application captured at a point during execution. For example, the information can be about the operating system, the application environment, threads, stacks, locks, and memory.

The exact contents depend on the platform on which you are running. By default, a Javadump occurs when the JVM terminates unexpectedly. A Javadump can also be triggered by sending specific signals to the JVM. Javadumps are human readable.

The preferred way to control the production of Javadumps is by enabling dump agents (see Using dump agents) using –Xdump:java: on application startup. You can also control Javadumps by the use of environment variables. See Environment variables and Javadump.

Default agents are in place that (if not overridden) create Javadumps when the JVM terminates unexpectedly or when an out-of-memory exception occurs. Javadumps are also triggered by default when specific signals are received by the JVM.

Note: Javadump is also known as Javacore. The default file name for a Javadump is javacore.<date>.<time>.<pid>.<sequence number>.txt. Javacore is NOT the same as a core file, which is generated by a system dump.

• Enabling a Javadump
  Javadumps are enabled by default. You can turn off the production of Javadumps with -Xdump:java:none.
• Triggering a Javadump
  Javadumps can be triggered by error conditions, or can be initiated in a number of ways to obtain diagnostic information.
• Interpreting a Javadump
  This section gives examples of the information contained in a Javadump and how it can be useful in problem solving.
• Environment variables and Javadump
  Although the preferred mechanism of controlling the production of Javadumps is now by the use of dump agents using -Xdump:java, you can also use the previous mechanism, environment variables.

Parent: Using diagnostic tools

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.