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 <[email protected]>
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 <[email protected]>
> To: 'Tomcat Users List' <[email protected]>
> 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: [email protected]
> > 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: [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]
