Re: All Threads Busy Message

2010-08-18 Thread JebaB
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 serve

Re: All Threads Busy Message

2010-08-18 Thread Christopher Schultz
-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

Re: All Threads Busy Message

2010-08-18 Thread JebaB
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 through the logging.properties. I am not seei

Re: All Threads Busy Message

2010-08-18 Thread Konstantin Kolinko
2010/8/18 JebaB : > > 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 acceptC

RE: All Threads Busy Message

2010-08-18 Thread JebaB
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 am not seeing the 'All Threads Busy' error messa

RE: All Threads Busy Message

2010-08-17 Thread Caldarale, Charles R
> 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 am not seeing the 'All Threads Busy' error message when all > the threads are in use or number of requests has exceeded the > maxThrea