try kill -QUIT <pid> This will give you thread dump of tomcat and of course that will include threads associated with your webapp On Fri, Oct 31, 2008 at 5:22 PM, AD <[EMAIL PROTECTED]> wrote: > Fair enough > > Tomcat 5.5, JVM 1.6, Redhat Enterprise 5, 8Gb Mem, 5Gb Heap. > > What is the best way to take a thread dump to see what processes are > waiting? We have a few web apps deployed and it has proven tricky for me to > narrow this down. We ran some load tests and encountered these issues. > > Whats the best way to get the thread dump and find out what process is hung > in the webapp ? > > Thx > Adam > > On Fri, Oct 31, 2008 at 7:31 PM, Caldarale, Charles R < > [EMAIL PROTECTED]> wrote: > >> > From: AD [mailto:[EMAIL PROTECTED] >> > Subject: All threads (200) are currently busy >> >> First, you need to provide some environmental information: Tomcat version, >> OS, JVM version, etc. >> >> > I am trying to find out after doing some load testing why >> > tomcat is getting hung up on some threads. >> >> Put the blame where it belongs: you webapp is getting hung up, not Tomcat. >> >> Take a thread dump and see where the threads are stuck. >> >> - Chuck >> >> >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY >> MATERIAL and is thus for use only by the intended recipient. If you received >> this in error, please contact the sender and delete the e-mail and its >> attachments from all computers. >> >> --------------------------------------------------------------------- >> 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]
