Leon Rosenberg wrote:
>> How best can I find the troubled thread on a running production system?
>
> kill -QUIT
>
> the thread dump will be printed into the catalina.out
Best to take several (eg 30 thread dumps ~10 seconds apart.
Mark
>
> Its best to restart the server after the thread dump,
F.ex. from my toy machine;
$ ps -fLp 7044
UIDPID PPID LWP C NLWP STIME TTY TIME CMD
tomcat7044 1 7044 0 40 2008 ?00:00:12 /usr/lib/jvm/java/bin
tomcat7044 1 7118 0 40 2008 ?00:02:58 /usr/lib/jvm/java/bin
tomcat7044 1 7119 0
David Wall wrote:
> We are running Tomcat 5.5.27 on Linux 2.6.18-53.1.4.el5xen (Red Hat
> 4.1.2-14) with Java 1.6.0_05 (32 bit) in a Xen virtualization
> environment (not my server, so unsure what version that is). It has 3
> webapps running, two of ours and Tomcat's manager.
>
> Normally, when w
> How best can I find the troubled thread on a running production system?
kill -QUIT
the thread dump will be printed into the catalina.out
Its best to restart the server after the thread dump, but since it's
handing anyway...
also include the heap info: jmap -heap
regards
Leon
-
We are running Tomcat 5.5.27 on Linux 2.6.18-53.1.4.el5xen (Red Hat
4.1.2-14) with Java 1.6.0_05 (32 bit) in a Xen virtualization
environment (not my server, so unsure what version that is). It has 3
webapps running, two of ours and Tomcat's manager.
Normally, when we run 'top', Java and it's
