How to gather heap dump on JVM out of memory error

For On-Prem servers:

Oracle Java Virtual Machine provides a JVM modifier to gather this information.
To apply this modifier to the JVM used by Mule, you can set a parameter in /conf/wrapper.conf which automatically triggers the creation of a heap dump during:

wrapper.java.additional.<n>=-XX:+HeapDumpOnOutOfMemoryError 
wrapper.java.additional.<n>=-XX:HeapDumpPath=path/to/dumps/dump.hprof

If no path is defined for heap dump file will be created in the directory from which the Java process was launched. The heap dump file should then be generated as
Filename:
java_pid<pid>.hprof.<unique number>

For CloudHub:

1. Raise a case to MuleSoft Support to request enabling HeapDumpOnOutOfMemoryError on the CloudHub worker.
2. Once the error occurs, raise a severity 1 case to MuleSoft Support for production environments or a severity 2 case for non-production environments if the previous case has been closed. Then, MuleSoft Support team will be able to collect the requested heap dump.

For RTF

How to Get Heap Dump On Out Of Memory App Restart in RTF?

Related Articles

If your server is not responsive but you are not sure if it's a memory issue, please review this guide.