moskito can help. you could at least see which servlet is currently processing. http://moskito.java.dev.net
if you have a really 'few' requests you could also look into /manager/status.html if you have the manager installed. regards Leon On 8/17/06, Dragon Fly <[EMAIL PROTECTED]> wrote:
Quite a few servlets run on our production Tomcat (Tomcat 5.0.25/JDK 1.4 on Solaris 2.8). It appears that one of the servlets runs in a tight/infinite loop (i.e. > 90% CPU) and eventually brings down Tomcat. This problem occurs once every few days and is probably triggered by a user request. Is there an easy way to pin point which servlet is the culprit? I looked into profiling a little bit but wasn't sure how easy it is to set it up in the production environment. Thank you in advance for your help. _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
