IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Overview of the available diagnostic tools > Summary of cross-platform tooling

Trace formatting

JVM trace is a key diagnostic tool for the JVM. The IBM JVM incorporates a large degree of flexibility in determining what is traced and when it is traced. This flexibility enables you to tailor trace so that it has a relatively small effect on performance.

The IBM Virtual Machine for Java™ contains many embedded trace points. In this release, maximal tracing is enabled by default for a few level 1 tracepoints and exception trace points. Command-line options allow you to set exactly what is to be traced, and specify where the trace output is to go. Trace output is generally in an encoded format and requires a trace formatter to be viewed successfully.

In addition to the embedded trace points provided in the JVM code, you can place your own application trace points in your Java code. You can activate tracing for entry and exit against all methods in all classes. Alternatively, you can activate tracing for a selection of methods in a selection of classes. Application and method traces are interleaved in the trace buffers with the JVM embedded trace points. The tracing allows detailed analysis of the routes taken through the code.

Tracing is used mainly for performance and leak problem determination. Trace data might also provide clues to the state of a JVM before an unexpected termination or "hang".

Trace and trace formatting are IBM-specific; that is, they are present only in the IBM Virtual Machine for Java. See Using method trace and Tracing Java applications and the JVM for more details. Although trace is not easy to understand, it is an effective tool.

Parent: Summary of cross-platform tooling

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.