Generating a Thread Dump
If Confluence is performing poorly, behaving unexpectedly or stops responding and you can generate a thread dump to help diagnose the cause of the problem. Including a thread dump can be very useful to the Atlassian Support team when investigating your problems.
The thread dump shows the current state of each thread in the JVM, including a stack trace, so it needs to be taken while the application is experiencing problems.
Information about what locks are being held and waited upon by a thread are not included in the simple thread dump that you can generate from within Confluence. If you need this additional information, you'll need to generate a thread dump externally.
On this page:
Security considerations
Error rendering macro 'excerpt-include'
User 'null' does not have permission to view the page.
Generating a thread dump within Confluence
To generate a thread dump:
- Go to .
Error rendering macro 'excerpt-include'
User 'null' does not have permission to view the page.
- Choose Create Support Zip
- Make sure Thread Dumps is selected (you can deselect any other options that you don't want to include - if you're creating the support zip to provide to Atlassian Support, we recommend including as much information as possible)
- Click Create.
A zip file containing your thread dumps (and anything else you chose to include) will be saved to your home directory.
Generating a thread dump externally
If Confluence stops responding or you require information on locks being held and waited upon by threads, then use one of methods described in Generating a Thread Dump Externally.
Our support team may ask you to use this method if the simple thread dump generated within Confluence does not include enough information to diagnose the problem.
Generating a thread dump using the Performance Data Collector
Error rendering macro 'includeplus'
User 'anonymous' does not have permission to view the page with ID 959776935.