On Monday 24 November 2008 16:15:19 Martin Spinassi wrote:
Hi to all again!
Nov 24, 2008 1:51:54 PM org.apache.tomcat.util.threads.ThreadPool
logFull
SEVERE: All threads (200) are currently busy, waiting. Increase
maxThreads (200) or check the servlet status
Executor name=tomcatThreadPool
From: Rainer Frey [mailto:[EMAIL PROTECTED]
Subject: Re: All threads are busy
Does the AJP connector support the executor? I thought not.
The doc claims it does, but I haven't looked at the code to verify.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
From: Martin Spinassi [mailto:[EMAIL PROTECTED]
Subject: All threads are busy
Nov 24, 2008 1:51:54 PM org.apache.tomcat.util.threads.ThreadPool
logFull
SEVERE: All threads (200) are currently busy, waiting. Increase
maxThreads (200) or check the servlet status
And what does a thread dump
On Mon, 2008-11-24 at 09:19 -0600, Caldarale, Charles R wrote:
From: Martin Spinassi [mailto:[EMAIL PROTECTED]
Subject: All threads are busy
Nov 24, 2008 1:51:54 PM org.apache.tomcat.util.threads.ThreadPool
logFull
SEVERE: All threads (200) are currently busy, waiting. Increase
From: Martin Spinassi [mailto:[EMAIL PROTECTED]
Subject: RE: All threads are busy
I should get the same errors using ports 80 or 8080, and I get
completely different results.
Connector executor= tomcatThreadPool port=8009 protocol=AJP/1.3
redirectPort=8443 /
Just for grins, take out
On Mon, 2008-11-24 at 09:33 -0600, Caldarale, Charles R wrote:
From: Martin Spinassi [mailto:[EMAIL PROTECTED]
Subject: RE: All threads are busy
I should get the same errors using ports 80 or 8080, and I get
completely different results.
Connector executor= tomcatThreadPool port=8009
