[FishEye Knowledge Base]
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.
If you are not running FishEye via run.bat, click on the console and press
Find the process ID of the JVM and use the ps command to get list of all processes:
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.
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:
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.