tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: AccessLogValve enhancement
Date Sun, 19 Feb 2012 17:20:23 GMT
Mark,

On 2/15/12 4:33 PM, Mark Thomas wrote:
> I also be +1 to considering making this the sole way AccessLogValve
> logging may be output.

The only possible reason why we wouldn't want to do this is that lots of
users simply cannot figure out how to configure the loggers. Yes, it's
really not all that hard and it's fairly well-documented, but at least
with the output file name in the <Valve> attributes, there's no question
where the log messages are going.

Philosophically, I'm not really sure why the flexibility of a
full-featured logging system (JULI, log4j, etc.) is required for access
logging: there's not much opportunity to use all the features they
provide (log level filtering, log-message aggregation to log files and
log-file multiplexing/splitting). Access logs typically log one thing
(accesses), log it all the time, and always write to the same log file.

I'm not adverse to the patch, I just don't really see a need for it.

-chris


Mime
View raw message