a) poorly designed reports which cause a buggy infinite loop
Release : All supported releases with Jaspersoft
Component : CA PPM SAAS JASPERSOFT
The easiest way to get thread dumps is via command-line on the appserver host, using jstack.exe which is in the bin dir of the JDK.
use ps -ef | grep java to get the pid, find JDK_HOME/bin, then issue cmd:
jstack -l <pid> <file-path>
like jstack -l 37320 > /opt/tmp/threadDump.txt
But you want maybe 5 or 6 across a single minute so we can see what methods might be stuck or active across that whole minute. So perhaps at a few different times during your "hang", you could capture 5 or 6 thread-dumps in 60-seconds worth of time.
It will be best to have these different sections of time in their own file, for example:
like jstack -l pid > /opt/tmp/threadDumpA.txt for 5 or 6 times in a single minute of the hang, then later
do jstack -l pid > /opt/tmp/threadDumpB.txt .... 5 or 6 times, then later
do jstack -l pid > /opt/tmp/threadDumpC.txt
If On Premise, also consider the following options:
1. An alternative to get thread-dumps from some means other than cmd line would be hooking up jvisualVM.exe via steps matching this:
2. You can also view thread activity in real-time via: