Thread issue - org.apache.tomcat.util.threads.ThreadPool logFull

[Curtis Garman]

Does anyone know what would cause the following error

Nov 4, 2009 9:30:28 AM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (150) are currently busy, waiting. Increase
maxThreads (150) or check the servlet status

I'm fronting apache tomcat 5.5.26 with apache 2.2.8 and mod_jk

My workers.properties file looks like

--------------------------------------------------
worker.list=ajp13,status

worker.status.type=status

worker.ajp13.type=ajp13
worker.ajp13.host=localhost
worker.ajp13.port=8009
worker.ajp13.socket_keepalive=1
worker.ajp13.connection_pool_timeout=600
worker.ajp13.connect_timeout=10000
worker.ajp13.prepost_timeout=10000
--------------------------------------------------

My AJP connector looks like

<Connector port="8009"
        maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
        connectionTimeout="600000" maxKeepAliveRequests="1"
        enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />

Is the 150 the error message refers to the maxThreads on my AJP
connector? Should this be increased?

Would enabling a log4j email appender cause this? I set one up today
but haven't gotten any email though.

--
Curtis Garman
Web Programmer
Heartland Community College

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Caldarale, Charles R]

> From: Curtis Garman [mailto:curt.garman@...]
> Subject: Thread issue - org.apache.tomcat.util.threads.ThreadPool
> logFull
>
> Does anyone know what would cause the following error
>
> Nov 4, 2009 9:30:28 AM org.apache.tomcat.util.threads.ThreadPool
> logFull
> SEVERE: All threads (150) are currently busy, waiting. Increase
> maxThreads (150) or check the servlet status

Likely that the threads are off stuck somewhere they shouldn't be.  Take a thread dump and find out what's going on.  No point in speculating when real data is easily available.
http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Curtis Garman]

Thanks for the link...I will look into this

Curtis

On Wed, Nov 4, 2009 at 12:20 PM, Caldarale, Charles R
<Chuck.Caldarale@...> wrote:

>> From: Curtis Garman [mailto:curt.garman@...]
>> Subject: Thread issue - org.apache.tomcat.util.threads.ThreadPool
>> logFull
>>
>> Does anyone know what would cause the following error
>>
>> Nov 4, 2009 9:30:28 AM org.apache.tomcat.util.threads.ThreadPool
>> logFull
>> SEVERE: All threads (150) are currently busy, waiting. Increase
>> maxThreads (150) or check the servlet status
>
> Likely that the threads are off stuck somewhere they shouldn't be.  Take a thread dump and find out what's going on.  No point in speculating when real data is easily available.
> http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F
>
>  - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
Curtis Garman
Web Programmer
Heartland Community College

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...