Confluence Docs 2.10 : Generating a Thread Dump
This page last changed on Oct 15, 2008 by jlargman.
If Confluence stops responding, or is performing poorly, you should create a thread dump to help Atlassian determine the cause of the problem. This will show the state of each thread in the JVM, including a stack trace and information about what locks the thread is holding and waiting for. Stack Traces and SecurityTo help debug support cases and provide legendary support, Confluence provides stack traces through the web interface when an error occurs. These stack traces include information about what Confluence was doing at the time, and some information about your deployment server. Only non-personal information is supplied such as operating system and version and Java version. With proper network security, this is not enough information to be considered dangerous. No usernames or passwords are included. Generating a Thread Dump on WindowsTo take a thread dump from Windows:
Generating a Thread Dump on Linux, including Solaris and other UnixesFind 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). OutputStandard 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. Thread Dump Tools
|
![]() |
Document generated by Confluence on Dec 03, 2008 15:17 |