-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tobias,
On 11/6/2009 8:56 AM, Tobias Crefeld wrote:
> Am Fri, 6 Nov 2009 08:24:14 +0100
> schrieb "Joan Monplet Ortega" :
>
>> Yeah, It's the one Tomcat. We have 4GB RAM on production Server and
>> We run it with 1GB.
>
> Not too much RAM... how man
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 11/6/2009 3:02 AM, André Warnier wrote:
> But, during a keepalive connection, usually the server needs to dedicate
> one process, or child or thread, to this connection. So this
> child/thread is blocked, and cannot server requests from oth
threads (700) are currently busy, waiting. Increase
maxThreads (700) or check the servlet status
Joan Monplet Ortega wrote:
> Yeah, It's the one Tomcat. We have 4GB RAM on production Server and We run it
> with 1GB.
>
> The version Tomcat is "Apache Tomcat/6.0.18".
>
>
As Charles suggested, you need a thread dump. There is too much
complexity in your setup to be able to find your problem without
actually inspecting the machine, but a thread dump can take you right
to the source of the problem in a matter of minutes.
--
Joan Monplet Ortega wrote:
Yeah, It's the one Tomcat. We have 4GB RAM on production Server and We run it
with 1GB.
The version Tomcat is "Apache Tomcat/6.0.18".
Also, We're working with Lucene but I'm not sure that the problem is here.
We're looking Server Status from Apache Web Server and We
e-sa.com]
Enviado el: jueves, 05 de noviembre de 2009 23:52
Para: Tomcat Users List
Asunto: Re: SEVERE: All threads (700) are currently busy, waiting. Increase
maxThreads (700) or check the servlet status
Joan Monplet Ortega wrote:
>
> SEVERE: All threads (700) are currently busy, waiting
> From: Joan Monplet Ortega [mailto:j...@solostocks-int.com]
> Subject: SEVERE: All threads (700) are currently busy, waiting.
> Increase maxThreads (700) or check the servlet status
>
> We have Apache Web Server & Tomcat 6.x, both are connected throws
> mod_proxy_ajp.
Joan Monplet Ortega wrote:
SEVERE: All threads (700) are currently busy, waiting. Increase
maxThreads (700) or check the servlet status
That sounds like a lot of threads.
And we checked all servlets and we are sure that all cursors to database
are closed (statement, resultset, etc
Hi,
We have Apache Web Server & Tomcat 6.x, both are connected throws
mod_proxy_ajp.
We have one instance Tomcat and different appBase (webapps).
We have a fatal problem, our Tomcat throws the next exception:
SEVERE: All threads (700) are currently busy, waiting. Incr
