You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Paul Grimwood <P....@gns.cri.nz> on 2005/04/20 06:07:10 UTC
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 60000 (but ours is set at 20000
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: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: All threads (250) are currently busy
Posted by farhad <fc...@comcast.net>.
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: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: All threads (250) are currently busy
Posted by Fadwa Barham <fa...@najah.edu>.
I forgot to say that I'm using windows not linux
----- Original Message -----
From: "Fadwa Barham" <fa...@najah.edu>
To: "Tomcat Users List" <to...@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" <fc...@comcast.net>
> To: "Tomcat Users List" <to...@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 60000 (but ours is set
>>>at 20000 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: tomcat-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: All threads (250) are currently busy
Posted by Fadwa Barham <fa...@najah.edu>.
Hi,
I have the same problem, I read the reply, and I want to ask, how to use
SIGQUIT?
regards
----- Original Message -----
From: "farhad" <fc...@comcast.net>
To: "Tomcat Users List" <to...@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 60000 (but ours is set at 20000
>>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: tomcat-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: All threads (250) are currently busy
Posted by farhad <fc...@comcast.net>.
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 60000 (but ours is set at 20000
>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: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: AW: All threads (250) are currently busy
Posted by Patty O'Reilly <or...@qualcomm.com>.
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 <zk...@intland.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: 'Tomcat Users List' <to...@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:P.Grimwood@gns.cri.nz]
> > 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 60000 (but ours is set at 20000
> > 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: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: All threads (250) are currently busy
Posted by Fadwa Barham <fa...@najah.edu>.
what's the correct configuration of the connector?
Regards
----- Original Message -----
From: "Zsolt Koppany" <zk...@intland.com>
To: "'Tomcat Users List'" <to...@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:P.Grimwood@gns.cri.nz]
>> 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 60000 (but ours is set at
>> 20000
>> 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: tomcat-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
AW: All threads (250) are currently busy
Posted by Zsolt Koppany <zk...@intland.com>.
We had the same problem, but after configuring the apache connector
correctly the problem disappeared.
Zsolt
> -----Ursprüngliche Nachricht-----
> Von: Paul Grimwood [mailto:P.Grimwood@gns.cri.nz]
> 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 60000 (but ours is set at 20000
> 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: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org