RE: All threads (250) are currently busy
You can use the tomcat manager application to find out which threads are busy. And secondly send a SIGHUP to the JVM and it will do a thread dump allowing you to work out what your threads are doing. You possibly have some kind of thread leak causing you to run out. Ta Matt -Original Message- From: Paul Grimwood [mailto:[EMAIL PROTECTED] Sent: 26 April 2005 21:27 To: Tomcat Users List Subject: Re: All threads (250) are currently busy This post has gone quiet, yet this is still a major problem for us in out live environment. Does anyone know the reason/solution (please see original post)? If so, please be more expansive than saying 'if you set it up right, it will work'. cheers Paul Patty O'Reilly [EMAIL PROTECTED] 21/04/2005 11:50 Please respond to Tomcat Users List To: Tomcat Users List tomcat-user@jakarta.apache.org cc: Subject:Re: AW: All threads (250) are currently busy Can you share your apache connector config? On Wed, 20 Apr 2005, Zsolt Koppany wrote: Date: Wed, 20 Apr 2005 11:08:33 +0200 From: Zsolt Koppany [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Subject: AW: All threads (250) are currently busy We had the same problem, but after configuring the apache connector correctly the problem disappeared. Zsolt -Ursprüngliche Nachricht- Von: Paul Grimwood [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 20. April 2005 06:07 An: tomcat-user@jakarta.apache.org Betreff: All threads (250) are currently busy Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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: AW: All threads (250) are currently busy
This post has gone quiet, yet this is still a major problem for us in out live environment. Does anyone know the reason/solution (please see original post)? If so, please be more expansive than saying 'if you set it up right, it will work'. cheers Paul Patty O'Reilly [EMAIL PROTECTED] 21/04/2005 11:50 Please respond to Tomcat Users List To: Tomcat Users List tomcat-user@jakarta.apache.org cc: Subject:Re: AW: All threads (250) are currently busy Can you share your apache connector config? On Wed, 20 Apr 2005, Zsolt Koppany wrote: Date: Wed, 20 Apr 2005 11:08:33 +0200 From: Zsolt Koppany [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Subject: AW: All threads (250) are currently busy We had the same problem, but after configuring the apache connector correctly the problem disappeared. Zsolt -Ursprüngliche Nachricht- Von: Paul Grimwood [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 20. April 2005 06:07 An: tomcat-user@jakarta.apache.org Betreff: All threads (250) are currently busy Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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: AW: All threads (250) are currently busy
On 4/26/05, Paul Grimwood [EMAIL PROTECTED] wrote: This post has gone quiet, yet this is still a major problem for us in out live environment. Does anyone know the reason/solution (please see original post)? If so, please be more expansive than saying 'if you set it up right, it will work'. Have their been any application changes in the same time period of moving servers? Something that might not be releasing threads? You are obviously hitting the maxThreads parameter in your connector but why remains a mystery... Also you shouldn't need to define the AJP connector if you are running standalone, also what does your HTTPS connector look like? Are you using HTTPS? If not try removing the redirectPort parameter from your HTTP connector but I don't think that is affecting your current problem. Regards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: All threads (250) are currently busy
I don't know what kind of application you are running, but most likely you have a resource leak; Do a thread dump and see what your threads are waiting for. Most likely they are just in wait state and no CPU usage. It could be cause by lots of things. One problem could be using jdbc and not closing your connection or returning it to your pool. For testing reduce your resource limit, don't increase it (reduce Max thread, and connection pool). This would cause system hangs faster. Send a SIGQUIT signal to VM and look at state of your threads and its location (don't post your thread dump!) Paul Grimwood wrote: Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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 (250) are currently busy
Hi, I have the same problem, I read the reply, and I want to ask, how to use SIGQUIT? regards - Original Message - From: farhad [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Wednesday, April 20, 2005 9:50 AM Subject: Re: All threads (250) are currently busy I don't know what kind of application you are running, but most likely you have a resource leak; Do a thread dump and see what your threads are waiting for. Most likely they are just in wait state and no CPU usage. It could be cause by lots of things. One problem could be using jdbc and not closing your connection or returning it to your pool. For testing reduce your resource limit, don't increase it (reduce Max thread, and connection pool). This would cause system hangs faster. Send a SIGQUIT signal to VM and look at state of your threads and its location (don't post your thread dump!) Paul Grimwood wrote: Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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: All threads (250) are currently busy
I forgot to say that I'm using windows not linux - Original Message - From: Fadwa Barham [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Wednesday, April 20, 2005 11:36 AM Subject: Re: All threads (250) are currently busy Hi, I have the same problem, I read the reply, and I want to ask, how to use SIGQUIT? regards - Original Message - From: farhad [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Wednesday, April 20, 2005 9:50 AM Subject: Re: All threads (250) are currently busy I don't know what kind of application you are running, but most likely you have a resource leak; Do a thread dump and see what your threads are waiting for. Most likely they are just in wait state and no CPU usage. It could be cause by lots of things. One problem could be using jdbc and not closing your connection or returning it to your pool. For testing reduce your resource limit, don't increase it (reduce Max thread, and connection pool). This would cause system hangs faster. Send a SIGQUIT signal to VM and look at state of your threads and its location (don't post your thread dump!) Paul Grimwood wrote: Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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]
AW: All threads (250) are currently busy
We had the same problem, but after configuring the apache connector correctly the problem disappeared. Zsolt -Ursprüngliche Nachricht- Von: Paul Grimwood [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 20. April 2005 06:07 An: tomcat-user@jakarta.apache.org Betreff: All threads (250) are currently busy Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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 (250) are currently busy
what's the correct configuration of the connector? Regards - Original Message - From: Zsolt Koppany [EMAIL PROTECTED] To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Sent: Wednesday, April 20, 2005 11:08 AM Subject: AW: All threads (250) are currently busy We had the same problem, but after configuring the apache connector correctly the problem disappeared. Zsolt -Ursprüngliche Nachricht- Von: Paul Grimwood [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 20. April 2005 06:07 An: tomcat-user@jakarta.apache.org Betreff: All threads (250) are currently busy Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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: All threads (250) are currently busy
It doesn't matter what platform your running on. On linux you can use kill -s SIGQUIT pid on window box if you have cygwin you can do the same and if you do not just do a google search and there are lots of C code that does that, you can look at signal.h or sites like http://www.csl.mtu.edu/cs4411.ck/www/NOTES/signal/kill.html has actual code for you. I haven't tried their code, but I used to have one myself. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: All threads (250) are currently busy
Zsolt, looks like i am not alone in this continuing problem, and thanks for the post. I should probably add that we use Tomcat in standalone mode as both web server and servlet engine and don't go though an apache web server. Here are the relevant bits from the Tomcat server xml. N.B Apache connector is still specified even though we are not going through an Apache web server. !-- Define a non-SSL HTTP/1.1 Connector on port 80 -- Connector port=80 maxThreads=250 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true / !-- Define an AJP 1.3 Connector on port 8009 -- Connector port=8009 enableLookups=false redirectPort=8443 protocol=AJP/1.3 / Does this look correct? Paul Zsolt Koppany [EMAIL PROTECTED] 20/04/2005 21:08 Please respond to Tomcat Users List To: 'Tomcat Users List' tomcat-user@jakarta.apache.org cc: Subject:AW: All threads (250) are currently busy We had the same problem, but after configuring the apache connector correctly the problem disappeared. Zsolt -Ursprüngliche Nachricht- Von: Paul Grimwood [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 20. April 2005 06:07 An: tomcat-user@jakarta.apache.org Betreff: All threads (250) are currently busy Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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: AW: All threads (250) are currently busy
Can you share your apache connector config? On Wed, 20 Apr 2005, Zsolt Koppany wrote: Date: Wed, 20 Apr 2005 11:08:33 +0200 From: Zsolt Koppany [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Subject: AW: All threads (250) are currently busy We had the same problem, but after configuring the apache connector correctly the problem disappeared. Zsolt -Ursprüngliche Nachricht- Von: Paul Grimwood [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 20. April 2005 06:07 An: tomcat-user@jakarta.apache.org Betreff: All threads (250) are currently busy Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - 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]
All threads (250) are currently busy
Tomcat hangs intermittently (1 to 10 days) with the following message in catalina.out 20/04/2005 13:48:09 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status We are running tomcat 5.5.7 on jdk1.5.0_02 under Redhat Linux Fedora Core 2 against an Oracle9 DB. I have seen various posts to this with suggestions including setting Linux threads with LD_ASSUME_KERNEL (tried but problem still exists) and setting connection timeout in server.xml from 0 to 6 (but ours is set at 2 already). And we have already upgraded to latest Tomcat and JRE to no avail. Despite reviewing the mailing list over the past 18 to 24 months, i am none the wiser. The problem started around the time we deployed the code onto a new server running a later Linux version but this could be a red herring and I suspect it is a database connection issue. Has anyone got any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
