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),
Martin Gainty wrote:
>
> your diagnostic appears out of sync with your source. where did you
> acquire the source?
>
The app is deployed under the the binary distribution gotten from the web
site (http://tomcat.apache.org/download-55.cgi). We do not compile from the
source, at least not yet. I
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
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) {
| 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
