> From: Etienne Lacombe [mailto:[EMAIL PROTECTED] > Subject: Tomcat 5.5.20 Stops Responding > > I followed your advice and killed the JVM so as to get the > stack trace when it stopped responding this afternoon.
It's not actually necessary to terminate the process in order to trigger a thread dump. > 3:27 org.apache....ThreadPool logFull > All threads (250) are currently busy, waiting. Increase > maxThreads (250) or check the servlet status. Do you really expect to have 250 active connections? Or are the threads stuck waiting on something to unlock? If you have keep-alives enabled and 250 active clients, and are not using the APR connector, then there will be a Tomcat thread dedicated to each active connection. > 3:41 - the stack trace dump... All threads are either > TIMED_WAITING, RUNNABLE or WAITING. That's pretty much all the states you're going to see. The real question is what are the threads in the WAITING state waiting for? Check the objects they're waiting on, and see if you have a deadlock situation in your webapp, or perhaps an unresponsive external resource (e.g., data base server). Yet another possibility is that you're not closing data base connections properly, resulting in none being available for new requests. Missing try/finally clauses around data base requests is the usual culprit in the last case. - 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]
