Re: ThreadPool logFull issue

Caldarale, Charles R wrote: >> From: Phani Raj Kumar [mailto:bphanirajku...@gmail.com] >> Subject: ThreadPool logFull issue >> >> org.apache.tomcat.util.threads.ThreadPool logFull >> >> SEVERE: All threads (150) are currently busy, waiting. > > Take a

RE: ThreadPool logFull issue

> From: Phani Raj Kumar [mailto:bphanirajku...@gmail.com] > Subject: ThreadPool logFull issue > > org.apache.tomcat.util.threads.ThreadPool logFull > > SEVERE: All threads (150) are currently busy, waiting. Take a thread dump and find out what the threads are doing. (The &

ThreadPool logFull issue

Hi Friends, I have found an exception( org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (150) are currently busy, waiting. Increase maxThreads (150) ) in my Tomcat server in last weekend. Ideall no body was using the application that time and this error came up. Could you p

Re: Realtime notification of ThreadPool logFull

Hi Jeff, jwboring schrieb: > private static void logFull(Log loghelper, int currentThreadCount, > int maxThreads) { > if( logfull ) { > log.error(sm.getString("threadpool.busy", >new Integer(currentThreadCount),

Re: Realtime notification of ThreadPool logFull

the same strange log. Jeff -- View this message in context: http://www.nabble.com/Realtime-notification-of-ThreadPool-logFull-tf2654425.html#a7424775 Sent from the Tomcat - User mailing list archive at Nabble.com. - To sta

Re: Realtime notification of ThreadPool logFull

ct: RE: Realtime notification of ThreadPool logFull > > > Nelson, Tracy wrote: >> Why not just grab the source > > I looked at the source (org.apache.tomcat.util.threads.ThreadPool) and it IS > logging to the commons logger - see below. > > private static void

RE: Realtime notification of ThreadPool logFull

E: All threads (10) are currently busy, waiting. Increase maxThreads." What gives? I am getting other normal info, etc ... level messages but not this one. Using v5.5.17. Jeff -- View this message in context: http://www.nabble.com/Realtime-notification-of-ThreadPool-logFull-tf2654425.html#a

RE: Realtime notification of ThreadPool logFull

| From: jwboring [mailto:[EMAIL PROTECTED] | Sent: Friday, 17 November, 2006 10:39 | | I need to be notified when ever a Tomcat v5.5 server is over the | threadpool | limit. I am already monitoring log4j log messages but the logFull message | appears to me to be a System.out log, by-passing log4j

Realtime notification of ThreadPool logFull

org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (10) are currently busy, waiting. Increase maxThreads If my above assumption is correct, how can I monitor ThreadPool logFull messages without reading the catalina.out file and parsing? Also, I'm aware of the ThreadPool mbean and already use JMX to query

ThreadPool logFull

I was stress-testing for our web application we always meet this TreadPool logFull. I have been doing some research and found our I can change the maximum number of thread in the server.xml. However, surfing the net i found some said that is not the real solution. I am not sure why and if anyone

Re: ThreadPool logFull, Tomcat not responding anymore

"Konrath Thomas" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi .. > > > We have a problem on our product server with our web application (which > is too complicated to go into the details of here). > Every day at least once our web application is mysteriously hanging. The > app

ThreadPool logFull, Tomcat not responding anymore

Hi .. We have a problem on our product server with our web application (which is too complicated to go into the details of here). Every day at least once our web application is mysteriously hanging. The application don't seem to crash or emit error messages, it just stop responding. In the c