If your VM has a deadlock next time, send it a
signal: kill -QUIT {PID}
The most VM's I know, will answer with a stack
trace for each thread in the error log.
This way you will not only see how many threads
there are, but also what they are doing.
This information might help to decide which
breakpoints you should set, if you want to use
a debugger.
> -----Urspr�ngliche Nachricht-----
> Von: Ivan E. Markovic [mailto:[EMAIL PROTECTED]]
> Gesendet: Montag, 23. Juli 2001 13:28
> An: [EMAIL PROTECTED]
> Betreff: Tracking Threads inside Tomcat
> Wichtigkeit: Hoch
>
>
> I hope that someone will be able to help.
>
> I have tomcat 3.2 running on a Sun Solaris platform and on my Mac
> OS-X. But after 5 to 10 hours Tomcat reaches some kind of deadlock on
> the Sun. Now I know that this is NOT a Tomcat issue, it is my code.
>
> But due to the length of time it takes to get to this stage it is
> very hard to debug. But I believe that it is a problem related to
> Threads not completing; for some reason. is there any way that I can
> trace the Threads, check their Stack Trace or something? I only have
> access remotely via a terminal window.
>
> Thank you.
>
> I v a n ...
> Ivan Markovic
> SculptLight
> http://www.sculptlight.com
> (+353) 87 2939256
> (+353) 1 2982205
>
> 114 Lower Churchtown Rd,
> Dublin 14,
> Ireland.
>
> --
>
