Confluence 3.5 : Generating a Heap Dump
This page last changed on Jan 10, 2011 by rhartono.
Sometimes you may see that Confluence is holding onto a chunk of memory over a period of time (for example, tenured space is increasing close to Xmx). In such a situation, it is useful to find out what is stacking up in the memory by analysing the heap dump. On this page:
Automatically Generating a Heap Dump when Confluence Hits OutOfMemory ErrorTypically, we would like to analyse the heap dump produced when Confluence died from an OutOfMemory Error. For this, you can add additional JVM parameters like below: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<path to this heap dump file> If you do not set the HeapDumpPath parameter, by default the heap dump will be saved in the folder where Tomcat is run from. Manually Generating a Heap Dump when Confluence Stops RespondingIt is also possible to get a heap dump manually using a JDK bundled tool called jmap, although we recommend that you use the automatic method above for best result. For UNIX and UNIX-Based Operating Systems: $JAVA_HOME/bin/jmap -dump:format=b,file=heap.bin <pid> For Windows: %JAVA_HOME%\bin\jmap -dump:format=b,file=heap.bin <pid> To find out the process ID for your Java process in Windows, you can use Process Explorer from Microsoft. This is what it looks like:
Submitting a Heap Dump to Atlassian SupportPlease zip the file and then send it to Atlassian Support. RELATED TOPICSGetting Java Crash Log File |
![]() |
Document generated by Confluence on Mar 16, 2011 18:52 |