You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jeff Genender <jg...@apache.org> on 2006/04/06 04:52:17 UTC
Tomcat access logs
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
Re: Tomcat access logs
Posted by Dain Sundstrom <da...@iq80.com>.
+1
-dain
On Apr 5, 2006, at 7:52 PM, 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
Re: Tomcat access logs
Posted by Jeff Genender <jg...@apache.org>.
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 <ma...@hogstrom.org> 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
>>>
>>>
>>>
Re: Tomcat access logs
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
+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 <ma...@hogstrom.org> 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
> >
> >
> >
>
Re: Tomcat access logs
Posted by Matt Hogstrom <ma...@hogstrom.org>.
+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
>
>
>
Re: Tomcat access logs
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Yes, I think Jetty shoudl work the same way, and if we get a
loggingEnabled flag in there or something similar, the console web
access log can work the same way as the web statistics in that if it's
not enabled it'll have a bit saying something to the effect of "The
web access log is currently disabled. Please consult your HTTP server
log if Geronimo is running through e.g. Apache or IIS, or else [Enable
Access Log]" (that last bit a link or button).
Thanks,
Aaron
On 4/6/06, Paul McMahan <pa...@gmail.com> wrote:
> Sounds like a good idea. Questions:
>
> - should the access logs for jetty also be disabled by default (for
> consistency)
> - how should the web access log viewer in the console react to this change?
>
>
> Paul
>
> On 4/5/06, Jeff Genender <jg...@apache.org> 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
> >
>
Re: Tomcat access logs
Posted by Paul McMahan <pa...@gmail.com>.
Sounds like a good idea. Questions:
- should the access logs for jetty also be disabled by default (for
consistency)
- how should the web access log viewer in the console react to this change?
Paul
On 4/5/06, Jeff Genender <jg...@apache.org> 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
>