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.
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.
|
Typically you'll want to take several dumps about 10 seconds apart, in which case you can generate several dumps and output the stack traces to a single file as follows: |
ps -ef | grep java. |
kill -3 <pid> |
|
This will not kill your server (so long as you included the "-3" option, no space in between). |
Use jstack.
Ctrl + Alt + Del and find the Process ID of the JAVA (Confluence) process.adam@track:~$ jstack -l 22668 > threaddump.txt |
if the jstack executable is not in your $PATH, then please look for it in your <JDK_HOME>/bin directory |
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 |
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