tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Rossbach ...@objektpark.de>
Subject Re: mod_jk log level and logging issues
Date Thu, 10 Aug 2006 06:35:30 GMT
Hi Rainer,

really good idea to fix the worker logging
++1...

=== Peter

Rainer Jung schrieb:
> Hi,
>
> thanks for the feedback. Good info!
>
> fredk2 schrieb:
>   
>> 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 :-) 
>>     
>
> Grrrrr. You are right. A quick inspection of our code shows, that in
> fact: if the JkLogLevel directive is being used and it can not map the
> value to a log level, it will use info. If one does not use any
> JkLogLevel, then the code really looks like we fall through to debug.
> Bad. I'll double check and correct defaults to INFO.
>
>   
>> 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 myserver.mydom.com /myapp/jsp/hello 200
>> 0.000378 0 HTTP/1.1 GET
>> . . .
>>     
>
> Again you are right. We log the request before we change the status
> code. Not good. I'll try to improve this.
>
>   
>> 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.
>>     
>
> Why do you expect a 404 in case Tomcat is down? If the request matches
> mod_jk JkMount config, it should try to send to tomcat and the result
> would be some 50X?
>
>   
>> 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 :)
>>     
>
> Regards,
>
> Rainer
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>   


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message