Where does JBoss save the Heap Dump when using the `HeapDumpOnOutOfMemoryError` parameter?

Where is the Heap Dump Saved When Using the HeapDumpOnOutOfMemoryError Parameter in JBoss?

The -XX: HeapDumpOnOutOfMemoryError parameter enables the generation of a heap dump when a Java Virtual Machine (JVM) encounters an out-of-memory error. This dump provides valuable data for debugging and diagnosing memory issues in applications running on JBoss.

Dump Location

By default, the heap dump is saved in a file named java_<em>pid</em>.hprof in the working directory of the JVM. The <em>pid</em> represents the process ID of the JVM. This means that the heap dump will be saved in the same directory where the JBoss server is running.

Custom Dump Location

If desired, you can specify an alternative dump path using the -XX:HeapDumpPath= parameter. For instance, to specify a custom directory for the dump, you could use the following startup option:

-XX:HeapDumpPath=/disk2/dumps

This will save the heap dump in the /disk2/dumps directory.

Remote Access

If you are not logged into the Unix server through the console, you may not be able to access the dump file directly. In such cases, you can consider using a remote access tool such as Secure Shell (SSH) to connect to the server and retrieve the heap dump.

By customizing the dump path and using remote access tools, you can ensure that the heap dump is saved in a convenient location for troubleshooting memory issues in your JBoss applications.

The above is the detailed content of Where does JBoss save the Heap Dump when using the `HeapDumpOnOutOfMemoryError` parameter?. For more information, please follow other related articles on the PHP Chinese website!