You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by JebaB <je...@yahoo.com> on 2010/08/18 00:16:26 UTC

All Threads Busy Message

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 following
in the logging.properties file but I am not seeing the message. 

org.apache.tomcat.util.threads.level=FINEST
org.apache.tomcat.util.threads.ThreadPool.level=FINEST

I have confirmed Tomcat is seeing the logging.properties file by changing
the logging levels of other packages.

I am able to see the message in Tomcat 5.0 using log4j.

-- 
View this message in context: http://old.nabble.com/All-Threads-Busy-Message-tp29449303p29449303.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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


Re: All Threads Busy Message

Posted by JebaB <je...@yahoo.com>.
Sorry, I pasted the wrong config setting. I have been playing with both JULI
and Log4j. I am sure I am running out of connections as the load tester I am
using is showing connection failed errors when I increase the number of
threads to be more then the maxThreads + acceptCount values in the
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
> 
> If you're using JULI, then a log4j configuration isn't going to help
> much. Can you post all relevant config files?
> 
> One more silly question: are you sure you're running out of threads?
> Maybe you're not getting a message because it's not actually happening.
> 
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAkxsmtkACgkQ9CaO5/Lv0PDhLwCeJEdPY2Ya6zZNmZCH89dNvUlK
> Y+gAn2IHwIVVDFVQwZ5+lV7kXREyrflw
> =SsF2
> -----END PGP SIGNATURE-----
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/All-Threads-Busy-Message-tp29449303p29478292.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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


Re: All Threads Busy Message

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----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

If you're using JULI, then a log4j configuration isn't going to help
much. Can you post all relevant config files?

One more silly question: are you sure you're running out of threads?
Maybe you're not getting a message because it's not actually happening.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxsmtkACgkQ9CaO5/Lv0PDhLwCeJEdPY2Ya6zZNmZCH89dNvUlK
Y+gAn2IHwIVVDFVQwZ5+lV7kXREyrflw
=SsF2
-----END PGP SIGNATURE-----

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


Re: All Threads Busy Message

Posted by JebaB <je...@yahoo.com>.
I tried the following setting and still no luck.

log4j.logger.org.apache.tomcat.util.net=DEBUG


Konstantin Kolinko wrote:
> 
> 2010/8/18 JebaB <je...@yahoo.com>:
>>
>> 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
>> following
>> in the logging.properties file but I am not seeing the message.
>>
>> org.apache.tomcat.util.threads.level=FINEST
>> org.apache.tomcat.util.threads.ThreadPool.level=FINEST
>>
>> I have confirmed Tomcat is seeing the logging.properties file by changing
>> the logging levels of other packages.
>>
>> I am able to see the message in Tomcat 5.0 using log4j.
>>
> 
> org.apache.tomcat.util.threads.ThreadPool is not used in Tomcat 6 by
> default.
> 
> I think that you will be dealing with
> java.org.apache.tomcat.util.net.JIoEndpoint#createWorkerThread()
> which logs the following message:
> endpoint.info.maxThreads=Maximum number of threads ({0}) created for
> connector with address {1} and port {2}
> 
> That is, looking at the current tc6.0.x sources. Cannot say exactly
> about 6.0.18.
> 
> Best regards,
> Konstantin Kolinko
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/All-Threads-Busy-Message-tp29449303p29474187.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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


Re: All Threads Busy Message

Posted by Konstantin Kolinko <kn...@gmail.com>.
2010/8/18 JebaB <je...@yahoo.com>:
>
> 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 following
> in the logging.properties file but I am not seeing the message.
>
> org.apache.tomcat.util.threads.level=FINEST
> org.apache.tomcat.util.threads.ThreadPool.level=FINEST
>
> I have confirmed Tomcat is seeing the logging.properties file by changing
> the logging levels of other packages.
>
> I am able to see the message in Tomcat 5.0 using log4j.
>

org.apache.tomcat.util.threads.ThreadPool is not used in Tomcat 6 by default.

I think that you will be dealing with
java.org.apache.tomcat.util.net.JIoEndpoint#createWorkerThread()
which logs the following message:
endpoint.info.maxThreads=Maximum number of threads ({0}) created for
connector with address {1} and port {2}

That is, looking at the current tc6.0.x sources. Cannot say exactly
about 6.0.18.

Best regards,
Konstantin Kolinko

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


RE: All Threads Busy Message

Posted by JebaB <je...@yahoo.com>.
The server.xml has been uploaded. Thanks for your help.

n828cl wrote:
> 
>> From: JebaB [mailto:jebabhas@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 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.
> 
> Post your server.xml (without comments and with privileged information
> masked out) so we can see what the <Connector> elements look like.  Note
> that if you're using an <Executor>, that message will never appear.
> 
>  - 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@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 
> 
http://old.nabble.com/file/p29471839/server.xml server.xml 
-- 
View this message in context: http://old.nabble.com/All-Threads-Busy-Message-tp29449303p29471839.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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


RE: All Threads Busy Message

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: JebaB [mailto:jebabhas@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 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.

Post your server.xml (without comments and with privileged information masked out) so we can see what the <Connector> elements look like.  Note that if you're using an <Executor>, that message will never appear.

 - 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@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org