tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fredk2 <>
Subject mod_jk log level and logging issues
Date Tue, 08 Aug 2006 20:27:29 GMT


These following issues are observed with mod_jk 1.2.18 on Linux and Solaris
8 with apache 1.3.27 and 2.2.2 (4 combinations).

issue 1:

With mod_jk 1.2.15 i set my jk log level:

    JkLogFile logs/mod_jk.log
    #JkLogLevel info
    JkRequestLogFormat "%w %V %U %s %T %B %H %m"

While switching to 1.2.18 I read in the fine manual that the default log
level is info so I removed the directive, and.....oh my ! the default is now
debug :-) 

Not a big deal, but I do wonder a little bit if this is a problem in my
build only. Does anyone get the same result ?


issue 2:

When Tomcat is down I get the following mod_jk.log error mesg and
JkRequestLog entry:
. . .
[Tue Aug 08 14:34:33 2006] [23653:0000] [error] ajp_service::jk_ajp_common.c
(1794): Error connecting to tomcat. Tomcat is probably not started or is
listening on the wrong port. worker=myWorker failed
[Tue Aug 08 14:34:33 2006] myWorker /myapp/jsp/hello 200
0.000378 0 HTTP/1.1 GET
. . .

The JkRequestLog entry shows a http status "200" whereas the browser (apache
httpd) reports properly "503".
Also any url that would normally show a status of "404" show "200" when
tomcat is down.
This is a bit unexpected but it appears that 1.2.15 is doing the same. 
Hence a broken tomcat can actually make a log stat look very good :)

View this message in context:
Sent from the Tomcat - User forum at

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message