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

Introduction to the Diagnostics Collector

The Diagnostics Collector gathers the Java diagnostic files for a problem event.

The Java runtime environment produces multiple diagnostic files in response to events such as...

• General Protection Faults
• Out of memory conditions
• Receiving unexpected operating system signals

The Diagnostics Collector runs just after the Java runtime environment produces diagnostic files. It searches for...

• System dumps
• Java dumps
• heap dumps
• Java trace dumps
• Verbose GC log that match the time stamp for the problem event

If a system dump is found, then optionally the Diagnostics Collector can run the jextract command to post-process the dump and capture extra information.

The Diagnostics Collector produces a single .zip file containing all the diagnostic information for the problem event. Steps in the collection of diagnostic data are logged in a text file. At the end of the collection process, the log file is copied into the output .zip file.

The Diagnostic Collector creates a separate process for collecting the data and producing the .zip file. This process produces console output, including messages, that is written to the same console as the original Java application. Some of these messages might therefore appear in the console after the original Java process finishes and the command prompt is displayed.

The Diagnostics Collector also has a feature to give warnings if there are JVM settings in place that could prevent the JVM from producing diagnostic data. These warnings are produced at JVM start, so that the JVM can be restarted with fixed settings if necessary. The warnings are printed on stderr and in the Diagnostics Collector log file. Fix the settings identified by any warning messages before restarting your Java application. Fixing warnings makes it more likely that the correct data is available for IBM Support to diagnose a Java problem.

Parent: The Diagnostics Collector

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.