Did you look in all your log files (everything in log/) ? Try running interactively, via bin/catalina.sh run and then send it the QUIT.
FWIW, I have run hundreds of hours of load test against a dual Xeon (HT - reports 4 CPUs) box (Dell 2850) and had no problems under RHEL V.4 (actually running a pair of tomcats on the same box in a vertical cluster.) Tim -----Original Message----- From: Dave Pullin [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 18, 2006 1:55 PM To: Tomcat Users List Subject: RE: How to diagnose a TomCat hang? Thank you. I've now tried kill -QUIT. The java process didn't die and it didn't write anything to catalina.out. May be that indicates what is hung, if it's not catching the QUIT signal? -----Original Message----- From: Tim Lucia [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 18, 2006 1:37 PM To: 'Tomcat Users List' Subject: RE: How to diagnose a TomCat hang? kill -QUIT will cause a stack dump... including any Java deadlocks. -----Original Message----- From: Dave Pullin [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 18, 2006 1:33 PM To: users@tomcat.apache.org Subject: How to diagnose a TomCat hang? Briefly: Is there anyway to figure out what TomCat is doing, or trying to do, when it hangs and does not respond to any http or https request? Details: I am running Tomcat 5.1.12 on Redhat9 on a 4 processor server. I get frequent but random Tomcat hangs. It has not happened on a 1 processor system, with either Linux or Windows. I can force the hang to happen fairly reliably if I run tests to bombard the server with http requests (several per second). According to logs it happens after the end of processing one request and before the beginning the next. It is apparently not within application code, unless it's a finalizer. I have run a higher priority daemon thread in same JVM that just writes the time to a log file, and it hangs at the same time, so it could be the JVM that's hanging, or whatever does the real threading. Mostly, but not always, 'top' shows the 'java' process using 99.9% of CPU, and 2 of the 4 processors at about 40%. I can kill the java process with 'kill -9', but I can't figure what it was stuck doing. Any suggestions? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
