Yep...great idea...I'll throw that flag in.
Aaron Mulder wrote: > +1 on the concept > > Can we leave the valve in place but with some flag set so requests > pass through it but it just does nothing? It would be nice if the > console could have an "enable logging" checkbox and nicer still if it > could just toggle a property on the valve instead of needing to insert > or remove valves in the chain. Like a "loggingEnabled" property or > something. > > Thanks, > Aaron > > On 4/6/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: >> +1 to leave it off. Generally folks will front end the AppServer with >> Apache HTTP and use that for >> their access logging. >> >> Jeff Genender wrote: >>> A while back, someone had requested that the access logs for Tomcat be >>> turned on by default in Geronimo. This basically involved enabling the >>> Tomcat AccessLogValve, and this request was granted. >>> >>> Upon further review, it would seem that other application servers leave >>> this off by default. In fact, Tomcat itself leaves this off by default. >>> I suppose that the reason for this is most Java web implementations are >>> front-ended by a web server such as httpd, and the web server handles >>> these logs. >>> >>> Should we follow suit and by default keep the access logs turned off? >>> This seems to make more sense. >>> >>> Thoughts and opinions on this matter? >>> >>> Jeff >>> >>> >>>
