Re: Tomcat 5.5.20 Stops Responding
Yup that's what I thought was happening. When all threads are busy, tomcat can't accept any more requests. To an extent tomcat still accepts some request and waits for a thread to free up but eventually it'll reject the requests with a 50x error. Either the tomcat service is legitimately overloaded (over 250 concurrent requests) or a design issue is preventing threads from being freed for new requests. You'll have to do some profiling to determine which it is and the best way to fix it. Also see Chuck Caldarale's message regarding potential causes to look for. --David Etienne Lacombe wrote: David, I followed your advice and killed the JVM so as to get the stack trace when it stopped responding this afternoon. Here is what we had in the log before the stack trace: 3:27 org.apacheThreadPool logFull All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status. 3:27 to 3:41 A few log statements from our webapps 3:41 - the stack trace dump... All threads are either TIMED_WAITING, RUNNABLE or WAITING. Etienne - 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]
Re: Tomcat 5.5.20 Stops Responding
Hi Etienne, Etienne Lacombe schrieb: Hello, Setup Linux Tomcat 5.5.20 Java 1.6 Two ideas: (1) I am not shure if Tomcat 5.5.20 is compatible with Java 1.6. (2) Turn on the AccessLogValve in your server.xml config file, so you can see if the client requests attain your Tomcat. If not I would assume this has nothing to do with Tomcat. So I would check the firewall. -- Franck I would like some help in locating the cause of a problem on a Tomcat 5.5.20 server. The server runs fine for some days and then suddenly stops responding to requests - the client's browser waits for a respond and times out. On the server, there is no CPU usage. However, when trying to access any of the webapps, including the Manager, they all time out. We tried connecting to the JVM using the JConsole and we don't get a response to that either. I went through all the log files and could not find any significant error (no out-of-memory, etc). Only a few error in our program but nothing that would cause the whole server to freeze up. There were a few socket connection error but they were not near the time of the freeze per what I could see. If anybody could help me by directing me to what else I should look for, that would be greatly appreciated! Etienne - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Beste Grüße Franck Borel ** Dipl.-Hyd. Franck BorelTelefon: +49[0]761-203 3908 Universitätsbibliothek Fax: +49[0]761-203 3987 Werthmannsplatz 2 E-Mail : [EMAIL PROTECTED] WWW: http://www.ub.uni-freiburg.de D-79098 Freiburg ** - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.5.20 Stops Responding
Regarding the ideas: 1. tomcat 5.5 and java 1.6 should be fine together. 2. If all threads are busy, the AccessLogValve may not show anything. Something _seems_ to be causing your jdk to turn into a zombie. Sending a kill signal to the tomcat process so you get a thread dump is probably best. Can you post the last few messages of catalina.out? --David Franck Borel wrote: Hi Etienne, Etienne Lacombe schrieb: Hello, Setup Linux Tomcat 5.5.20 Java 1.6 Two ideas: (1) I am not shure if Tomcat 5.5.20 is compatible with Java 1.6. (2) Turn on the AccessLogValve in your server.xml config file, so you can see if the client requests attain your Tomcat. If not I would assume this has nothing to do with Tomcat. So I would check the firewall. -- Franck I would like some help in locating the cause of a problem on a Tomcat 5.5.20 server. The server runs fine for some days and then suddenly stops responding to requests - the client's browser waits for a respond and times out. On the server, there is no CPU usage. However, when trying to access any of the webapps, including the Manager, they all time out. We tried connecting to the JVM using the JConsole and we don't get a response to that either. I went through all the log files and could not find any significant error (no out-of-memory, etc). Only a few error in our program but nothing that would cause the whole server to freeze up. There were a few socket connection error but they were not near the time of the freeze per what I could see. If anybody could help me by directing me to what else I should look for, that would be greatly appreciated! Etienne - 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]
RE: Tomcat 5.5.20 Stops Responding
From: Etienne Lacombe [mailto:[EMAIL PROTECTED] Subject: Tomcat 5.5.20 Stops Responding I would like some help in locating the cause of a problem on a Tomcat 5.5.20 server. Any particular reason for reposting the exact same message when David S already suggested something to try? Why post if you're going to ignore the replies? - 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]
RE: Tomcat 5.5.20 Stops Responding
From: Etienne Lacombe [mailto:[EMAIL PROTECTED] Subject: Tomcat 5.5.20 Stops Responding I was sure my Email had not been sent so that's why I resent it. You can always check the archives to see if your message has made it to the rest of world: http://marc.info/?l=tomcat-user http://mail-archives.apache.org/mod_mbox/tomcat-dev/ - 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]
RE: Tomcat 5.5.20 Stops Responding
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.apacheThreadPool 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]
