If Confluence stops responding and you cannot access its integrated Generate Thread Dump feature, it is possible to create thread dumps outside the application. External thread dumps are also useful if you require information on locks being held or waited upon by threads.
To take a thread dump from Windows:
If you were asked by Atlassian technical support to create the thread dump, please take 2 to 3 thread dumps with a time interval in between (eg. 30 seconds) so we can see some patterns. Attach the log file to the support ticket.
Alternatively, if you are not running Confluence as a service, click on the console and press |
Find the process ID of the JVM and use the ps command to get list of all processes:
kill -3 <pid> |
Note: This will not kill your server (so long as you included the "-3" option, no space in between).
The thread dump will be printed to Confluence's standard output (catalina.out).
Standard logging for Confluence Stand-alone is sent to the atlassian-confluence.log, in the confluence-home directory, not in the confluence-install directory. Thread dumps are an exception since they dump the threads of the entire application server - they'll appear in the catalina.out file in the application directory's logs folder. You can search for the term "thread dump" in the log file for the beginning of the dump. Submit this along with the atlassian-confluence.log in your support ticket.
java.net