I have an application running on Tomcat 5.5 that periodically hangs in
our production environment. When I try any page in my application, my
web browser just waits for a page indefinitely. I can wait for an hour
and it will never respond (normally responds in 1-3 seconds).

I haven't reproduced this issue on my dev system.  Tomcat Manager
continues to respond correctly during this hang so Tomcat itself is
correctly configured and still functioning.

I see no errors in my log files or catalina.out. On the server status
page, I see this:
Max threads: 150 Min spare threads: 25 Max spare threads: 75 Current
thread count: 150 Current thread busy: 130

Does that imply a deadlock within the web application? My application
is somewhat complicated and not all written by me. This site is low
volume (typically 0-2 users are on at any given time), so I can't
imagine why 130 threads would be busy. How could I test if there is a
deadlock? Ideally I could see a stack trace of those busy threads.

Any other ideas?

Thanks!

Tomcat 5.5
JDK 1.5.08
Linux
JSF/Hibernate/Facelets

---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to