スレッド ダンプの外部での生成

If Fisheye stops responding or is showing poor performance, providing thread dumps to support can help diagnose the problem.

Generating a Thread Dump for Windows

To take a thread dump:

1. Visit http://www.adaptj.com/root/main/download and click Launch
2. Click Run for any security warnings
3. Select Process -> Thread Dump
4. Under Process Id, select the '...' button.
5. From the drop-down list, select the Confluence process. Users running Fisheye, select the 'Java ...' option.
6. Ensure that the "Thread dump" and "Keep Remote Thread Running" is selected.
7. Click OK to capture the thread dump.
8. Save the output to a file, eg 'threaddump.log'

If you were asked by Atlassian technical support to create the thread dump, please take 4 thread dumps with a time interval in between (eg. 30 secs) so we can see some patterns. Attach the log file to the support ticket.

Generating a Thread Dump on Linux, including Solaris and other Unixes

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 Fisheye's standard output (fisheye.out).
If you have trouble generating the thread dumps with this method, then use the method "Generating a Thread dump for Windows" as they can also apply for linux, etc.

出力

Standard logging for Fisheye is sent to the FISHEYE_INST/var/log/fisheye-debug.log.* files, in the FISHEYE_INST directory. Thread dumps are an exception since they dump the threads of the entire application server - they'll appear in the FISHEYE_INST/var/log/fisheye.out file. You can search for the term "thread dump" in the log file for the beginning of the dump.

Thread Dump Tools

• Samurai
• Thread Dump Analyzer TDA TDA 1.0 Final can be obtained from the java.net