Hi Bob,
Kill -3 <TOMCAT PID>
Will produce a stack trace in catalina.out
This problem is VERY most probably your code, and not tomcat, but a
stacktrace should show this.
ps auxwh
will also give you an indication, its probably just 1 thread pushing
you to such a high load.
As for "walking" through the code - don't forget this stuff is
multithreaded so its not so easy to walk through...
My bets are on an unsynchronized HashMap.
Cheers
Andrew
On 05/11/2007, at 10:44 PM, Sai Bobba wrote:
Many thanks. We've had several developers walk through the code to
try to
catch the possibity that the app may be sitting in a loop in some
situations. The code seems ok, and, as I indicated, we've never been
able to
reproduce the situation. I've searched the web for taking thread
dumps, as I
don't know how to do that, butg haven't been able to find anything.
Perhaps
you could give me a pointer if you have the time.
Thanks again for your attention.
Bob
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
