This is the documentation for FishEye 3.1. View the latest version of

Unknown macro: {spacejump}

or visit the current documentation home page.

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


(info) 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 for Windows

If you are not running FishEye via run.bat, click on the console and press <CTRL>+BREAK

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.

Jstack

Sun JDK 1.5 and above ship with native tool called jstack to perform thread dump. To use the tool find the Proccess ID and execute the command:

jstack <ProccessID>

Output

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

  • No labels

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.