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: 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]
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]
RE: RE: RE: All threads (150) are currently busy....
I have made tests of my solution. It runs more then week without problems. So, I have posted it now to the original mailing thread. But it solves only my particular situation. I am not sure if the solution can help you. I think that more usefull for you is the way I found the problem. I used kill -QUIT signal and from stack traces I recognized the reason (many thanks to Antonio Fiol). Lipi -Original Message- From: Pavle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 10:10 AM To: [EMAIL PROTECTED] Subject: 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]