tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Rossbach ...@objektpark.de>
Subject Re: svn commit: r531475 - in /tomcat/tc6.0.x/trunk: java/org/apache/catalina/valves/AccessLogValve.java java/org/apache/catalina/valves/mbeans-descriptors.xml webapps/docs/changelog.xml
Date Mon, 23 Apr 2007 16:59:44 GMT
You are right, but normally the apache produce the access logging.  
Sometimes I need a more application centric
monitoring log at tomcat side.  The admin don't want to restart the  
tomcat instance to this configuration change. OK, with JMX we can add  
and drop a complete AccessLogValve at runtime :-) But some people  
don't like those component creations at a running server :-)
With the new enabled flag the logging activation was really easy and  
configuration don't change. Admin can do it with a jmxproxy request  
at manager app or jconsole.

Peter



Am 23.04.2007 um 17:24 schrieb Remy Maucherat:

> Peter Rossbach wrote:
>> The idea behind the flag is to disable a accesslogger at server.xml.
>> As site become some perfornance problems you can enable access  
>> Logging by jmx and analyse the output on the fly.
>
> Mmm, ok, it's not a bad idea then. (normally, with all the  
> optimizations, access logging is cheap)
>
> Rémy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message