RE: RE: Tomcat 4.1.30 Hung!!! With High Traffic
Try to make kill -QUIT on the tomcat process. This will make a thread dump. Most probaly the Thread dum will appear in the catalina.out Check there to see if some of your threads are halting in some point in your code. Pavle -Original Message- From: Antonio Fiol Bonnn [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 8:35 AM To: Tomcat Users List Subject: Re: Tomcat 4.1.30 Hung!!! With High Traffic Innovest Ken wrote: I only use tomcat, without using Apache... Because my site are mainly jsp. Yes, I have a script to kill the tomcat server before starting again. And yes, I saw the 'All threads(150) are busy' error message. Innovest As Denise said, you seem to be maxing out your threads. Possible reasons include, but are most likely not limited to: - Too high load. --- Check with netstat -n --tcp if there are about so many (150) ESTABLISHED connections. If so, your load is too high. If not, suspect on servlets taking too long to respond and clients going away. - Servlet instances not finishing execution of doGet or doPost or whatever. --- Trace their starts and ends (possibly using a filter), and detect whether the number of still executing servlets is steadily increasing or not. If so, it will raise 150 and then you'll start getting errors and Tomcat will start not responding. The thread dump should tell you where the processors are stuck. Most of them in the same place? Then you know where to look at. - Database connections not working properly because of the firewall. --- Not only you have to check that your app is using connections properly, but also that your firewall does not drop them. There are some properties for DBCP (testWhileIdle, validationQuery, and all the eviction series, which I do not remember off-hand) that will help you attack this problem. Set testWhileIdle, and make it test connections every so often (say 3-5 minutes). Use a very simple query like SELECT 1 FROM DUAL (Oracle) or SELECT 1 (others that support it). This will refresh your firewall's activity maps. Also check that your firewall supports as many concurrent conenctions traversing it as you have (more than likely it does, but would be fatal if it does not). HTH, Antonio Fiol - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
All threads (150) are currently busy....
After several days of good woking my Tomcat 5.0.16 on RedHat 9.0 box stops accepting connection on SSL connector. In catalina.out I am recieving this message: SEVERE: All threads (150) are currently busy My server.xml file for SSL connector is the following: Connector port=8443 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true connectionTimeout=2 acceptCount=100 debug=0 scheme=https secure=true Factory clientAuth=false protocol=TLS keystoreFile=*** keystorePass=***/ /Connector I tried to put smaller connectionTimeout but it does not work too. I am not able to find anything on Google. Thanks Pavle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE: All threads (150) are currently busy....
The main problem is that there is no load on the serever when this occurs. Everything works perfectly during the normal working week. The message and the hunging occurs during weekends, when there is low traffic. Pavle -Original Message- From: rlipi [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 8:46 AM To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: All threads (150) are currently busy Hi, it means that all threads are currently performing some request. It can have two reasons: 1) High load of the server - requests come quicker than they are finished. You can increase maxThreads or you can look into your app why it takes so long time. 2) Some requests are not finished due to some bug in your app. On Linux you can send kill -QUIT to your Tomcat process. You will receive stack traces of all VM threads and you can see where the threads currently are. Lipi -Original Message- From: Pavle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 8:21 AM To: [EMAIL PROTECTED] Subject: All threads (150) are currently busy After several days of good woking my Tomcat 5.0.16 on RedHat 9.0 box stops accepting connection on SSL connector. In catalina.out I am recieving this message: SEVERE: All threads (150) are currently busy My server.xml file for SSL connector is the following: Connector port=8443 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true connectionTimeout=2 acceptCount=100 debug=0 scheme=https secure=true Factory clientAuth=false protocol=TLS keystoreFile=*** keystorePass=***/ /Connector I tried to put smaller connectionTimeout but it does not work too. I am not able to find anything on Google. Thanks Pavle - 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]
RE: RE: RE: All threads (150) are currently busy....
-Original Message- From: rlipi [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 9:40 AM To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: RE: All threads (150) are currently busy I had a bit similar problem - see How to limit time for Connector threads? tread in this mailing list. In the end I found that my thread is in java.net.SocketOutputStream.socketWrite0(Native Method) method. Probably reason was that server waited for timeout because client had broken connection. Stack trace of running threads was very useful. Lipi -Original Message- From: Pavle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 9:00 AM To: [EMAIL PROTECTED] Subject: RE: RE: All threads (150) are currently busy The main problem is that there is no load on the serever when this occurs. Everything works perfectly during the normal working week. The message and the hunging occurs during weekends, when there is low traffic. Pavle -Original Message- From: rlipi [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 8:46 AM To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: All threads (150) are currently busy Hi, it means that all threads are currently performing some request. It can have two reasons: 1) High load of the server - requests come quicker than they are finished. You can increase maxThreads or you can look into your app why it takes so long time. 2) Some requests are not finished due to some bug in your app. On Linux you can send kill -QUIT to your Tomcat process. You will receive stack traces of all VM threads and you can see where the threads currently are. Lipi -Original Message- From: Pavle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 8:21 AM To: [EMAIL PROTECTED] Subject: All threads (150) are currently busy After several days of good woking my Tomcat 5.0.16 on RedHat 9.0 box stops accepting connection on SSL connector. In catalina.out I am recieving this message: SEVERE: All threads (150) are currently busy My server.xml file for SSL connector is the following: Connector port=8443 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true connectionTimeout=2 acceptCount=100 debug=0 scheme=https secure=true Factory clientAuth=false protocol=TLS keystoreFile=*** keystorePass=***/ /Connector I tried to put smaller connectionTimeout but it does not work too. I am not able to find anything on Google. Thanks Pavle - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE: RE: All threads (150) are currently busy....
Really sorry for the previous mail. I have sent it by mistake. How did you resolve the problem. I have visited the thread you have suggested, but however I was unable to find the solution. Pavle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
