We have two versions, 4.1.29 and 5.0.28, Tomcat running in our environment.
In the 4.1.29, we are using the http10 connector. In the logs we see
messages when a connection is being refused when there are no more threads
available to process the request. We also see messages in the logs when
Tomcat
I am currently using Tomcat 6.0 and in the previous versions I have used, I
used to see a message when all the threads are in use and Tomcat was
rejecting connections due to no more available threads. I am not able to see
this message on Tomcat 6.0. I was able to add property in logging.properties
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jeba,
>
> On 6/15/2009 5:32 PM, JebaB wrote:
>> I am currently using Tomcat 6.0 and in the previous versions I have used,
>> I
>> used to see a message when all the threads are in use and Tomcat
Hello,
I am using Tomcat 6.0.18 with JDK 1.6 with the JULI. I have enabled proper
logging through the logging.properties. I am not seeing the 'All Threads
Busy' error message when all the threads are in use or number of requests
has exceeded the maxThreads and acceptCount values. I have set the f
The server.xml has been uploaded. Thanks for your help.
n828cl wrote:
>
>> From: JebaB [mailto:jebab...@yahoo.com]
>> Subject: All Threads Busy Message
>>
>> I am using Tomcat 6.0.18 with JDK 1.6 with the JULI.
>
> Why such an old level?
>
>> I
I tried the following setting and still no luck.
log4j.logger.org.apache.tomcat.util.net=DEBUG
Konstantin Kolinko wrote:
>
> 2010/8/18 JebaB :
>>
>> Hello,
>> I am using Tomcat 6.0.18 with JDK 1.6 with the JULI. I have enabled
>> proper
>> logging thro
server.xml.
Thanks.
Christopher Schultz-2 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jeba,
>
> On 8/18/2010 1:53 PM, JebaB wrote:
>> I tried the following setting and still no luck.
>>
>> log4j.logger.org.apache.tomcat.util.net=DEBUG
