your diagnostic appears out of sync with your source
where did you acquire the source?
M-
This e-mail communication and any attachments may contain confidential and
privileged information for the use of the
designated recipients named above. If you are not the intended recipient, you
are hereby notified that you have received
this communication in error and that any review, disclosure, dissemination,
distribution or copying of it or its
contents
----- Original Message -----
From: "jwboring" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Saturday, November 18, 2006 9:27 AM
Subject: 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 logFull(Log loghelper, int currentThreadCount,
> int maxThreads) {
> if( logfull ) {
> log.error(sm.getString("threadpool.busy",
> new Integer(currentThreadCount),
> new Integer(maxThreads)));
> logfull=false;
> } else if( log.isDebugEnabled() ) {
> log.debug("All threads are busy " + currentThreadCount + " " +
> maxThreads );
> }
> }
>
>
> But this is NOT the log I am getting in catalina.out. Instead, I am getting,
> "Nov 17, 2006 12:08:25 PM org.apache.tomcat.util.threads.ThreadPool logFull
> SEVERE: 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#a7419824
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
