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:
|
If you have a large Xmx size, please limit your Xmx size to 1024m. This will help to keep Confluence heap dump smaller while still containing sufficient information to analyse it. |
Typically, 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.
It 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:
Please execute the following command on a UNIX-based OS:
$JAVA_HOME/bin/jmap -dump:format=b,file=heap.bin <pid> |
For Windows:
Please find your Confluence process ID (see below) and then execute the command below on a Windows command line:
%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:
Please zip the file and then send it to Atlassian Support.
Getting Java Crash Log File
Memory usage and requirements
Garbage Collector Performance Issues
Generating a Thread Dump
Fix Out of Memory Errors by Increasing Available Memory