Re: All threads (150) are currently busy....
Hi Pavle, Do you use a database? Is there a firewall between Tomcat and the database? If both answers are yes, try using testWhileIdle, validationQuery, time between eviction runs (can't remember property name) and other DBCP properties. Other than that, my typical advice, which I learnt from Yoav Shapira IIRC, is (as Lipi told you), kill -QUIT and see what happens. Antonio Fiol Pavle wrote: 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 smime.p7s Description: S/MIME Cryptographic Signature
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: 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]
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]
RE: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status
We are using RedHat 9, Kernel 2.4.20-20.9. JVM 1.4.2_01-b06. We are using Postgres and created our own database connection pooling api. I will try setting the environment variable LD_ASSUME_KERNEL=2.4.1. When you refer to a 'thread dump' are you referring to running netstat and viewing the threads running on the ports Tomcat is set up on? Or is there another way to get a thread dump? (sorry, for my ignorance on linux) Thanks for the help. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Thursday, December 25, 2003 2:11 AM To: Tomcat Users List Subject: Re: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status alan sparago wrote: I am using Tomcat 5.0.16 standalone serving as both an http/https web server and servlet container. This error occurred in our QA environment and has caused Tomcat to hang and not service any requests. This error seemed to occur when no users were using the site at the time, but about 4 DAYS earlier we preformed a stress test simulating 1200 semi-simultaneous users and everything worked perfectly without any errors. Since the stress test we are only accessing the application as an occasional single user, the last time being about 8 hours prior to this error happening. Most parameters in the server.xml file are the default values (the maxThreads value is set to 150). Our log file is in xml format and contains the following error; loggerorg.apache.tomcat.util.threads.ThreadPool/logger levelSEVERE/level classorg.apache.tomcat.util.threads.ThreadPool/class methodlogFull/method thread13/thread messageAll threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status/message fyi. Nowhere in my application is the code creating any threads. If running Linux 2.4 with tweaks, and esp RH 9, use LD_ASSUME_KERNEL=2.4.1. This kind of report is not very useful without a thread dump once the issue occurs and all threads appear deadlocked, BTW. If there's actually a bug in the Tomcat code, then it's the only way to identify where it is. We are very close to our site being live so any help or information would be greatly appreciated. Would tomcat 4.1.29 be more stable? No, it is the same connector anyway. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - 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: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status
Hi, Have you taken a thread dump and checked as what are these threads waiting for before increasing the max-threads? Please specify the jdk version and OS too. In case you are using any databases, please also send in the details. Arnab From: alan sparago [mailto:[EMAIL PROTECTED] Sent: Thu 12/25/2003 12:45 AM To: [EMAIL PROTECTED] Cc: Dave McCuistion Subject: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status I am using Tomcat 5.0.16 standalone serving as both an http/https web server and servlet container. This error occurred in our QA environment and has caused Tomcat to hang and not service any requests. This error seemed to occur when no users were using the site at the time, but about 4 DAYS earlier we preformed a stress test simulating 1200 semi-simultaneous users and everything worked perfectly without any errors. Since the stress test we are only accessing the application as an occasional single user, the last time being about 8 hours prior to this error happening. Most parameters in the server.xml file are the default values (the maxThreads value is set to 150). Our log file is in xml format and contains the following error; loggerorg.apache.tomcat.util.threads.ThreadPool/logger levelSEVERE/level classorg.apache.tomcat.util.threads.ThreadPool/class methodlogFull/method thread13/thread messageAll threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status/message fyi. Nowhere in my application is the code creating any threads. We are very close to our site being live so any help or information would be greatly appreciated. Would tomcat 4.1.29 be more stable? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status
alan sparago wrote: I am using Tomcat 5.0.16 standalone serving as both an http/https web server and servlet container. This error occurred in our QA environment and has caused Tomcat to hang and not service any requests. This error seemed to occur when no users were using the site at the time, but about 4 DAYS earlier we preformed a stress test simulating 1200 semi-simultaneous users and everything worked perfectly without any errors. Since the stress test we are only accessing the application as an occasional single user, the last time being about 8 hours prior to this error happening. Most parameters in the server.xml file are the default values (the maxThreads value is set to 150). Our log file is in xml format and contains the following error; loggerorg.apache.tomcat.util.threads.ThreadPool/logger levelSEVERE/level classorg.apache.tomcat.util.threads.ThreadPool/class methodlogFull/method thread13/thread messageAll threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status/message fyi. Nowhere in my application is the code creating any threads. If running Linux 2.4 with tweaks, and esp RH 9, use LD_ASSUME_KERNEL=2.4.1. This kind of report is not very useful without a thread dump once the issue occurs and all threads appear deadlocked, BTW. If there's actually a bug in the Tomcat code, then it's the only way to identify where it is. We are very close to our site being live so any help or information would be greatly appreciated. Would tomcat 4.1.29 be more stable? No, it is the same connector anyway. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status
I am using Tomcat 5.0.16 standalone serving as both an http/https web server and servlet container. This error occurred in our QA environment and has caused Tomcat to hang and not service any requests. This error seemed to occur when no users were using the site at the time, but about 4 DAYS earlier we preformed a stress test simulating 1200 semi-simultaneous users and everything worked perfectly without any errors. Since the stress test we are only accessing the application as an occasional single user, the last time being about 8 hours prior to this error happening. Most parameters in the server.xml file are the default values (the maxThreads value is set to 150). Our log file is in xml format and contains the following error; loggerorg.apache.tomcat.util.threads.ThreadPool/logger levelSEVERE/level classorg.apache.tomcat.util.threads.ThreadPool/class methodlogFull/method thread13/thread messageAll threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status/message fyi. Nowhere in my application is the code creating any threads. We are very close to our site being live so any help or information would be greatly appreciated. Would tomcat 4.1.29 be more stable?
