DO NOT REPLY [Bug 20380] - AccessLogValve incorrectly calculates timezone

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 32714] - AccessLogValve cannot be extended as it is final

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 32714] New: - AccessLogValve cannot be extended as it is final

gzilla/show_bug.cgi?id=32714 Summary: AccessLogValve cannot be extended as it is final Product: Tomcat 5 Version: 5.0.16 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Ca

DO NOT REPLY [Bug 32135] - AccessLogValve directory attribute ignores leading slash

gzilla/show_bug.cgi?id=32135 AccessLogValve directory attribute ignores leading slash [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 32135] New: - AccessLogValve directory attribute ignores leading slash

gzilla/show_bug.cgi?id=32135 AccessLogValve directory attribute ignores leading slash Summary: AccessLogValve directory attribute ignores leading slash Product: Tomcat 5 Version: 5.0.27 Platform: PC OS/Version: Windows XP Statu

DO NOT REPLY [Bug 20380] - AccessLogValve incorrectly calculates timezone

gzilla/show_bug.cgi?id=20380 AccessLogValve incorrectly calculates timezone [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PRO

Re: DO NOT REPLY [Bug 26171] - NullPointerException in AccessLogValve

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26171 NullPointerException in AccessLogValve [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 26171] - NullPointerException in AccessLogValve

gzilla/show_bug.cgi?id=26171 NullPointerException in AccessLogValve [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 26171] New: - NullPointerException in AccessLogValve

gzilla/show_bug.cgi?id=26171 NullPointerException in AccessLogValve Summary: NullPointerException in AccessLogValve Product: Tomcat 5 Version: 5.0.16 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority:

DO NOT REPLY [Bug 14281] - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 16400] - Allow AccessLogValve to ignore (not log) requests for particular URIs

gzilla/show_bug.cgi?id=16400 Allow AccessLogValve to ignore (not log) requests for particular URIs [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 16374] - Make access log filename date format configurable in AccessLogValve

gzilla/show_bug.cgi?id=16374 Make access log filename date format configurable in AccessLogValve [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 20380] - AccessLogValve incorrectly calculates timezone

gzilla/show_bug.cgi?id=20380 AccessLogValve incorrectly calculates timezone [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 20380] New: - AccessLogValve incorrectly calculates timezone

gzilla/show_bug.cgi?id=20380 AccessLogValve incorrectly calculates timezone Summary: AccessLogValve incorrectly calculates timezone Product: Tomcat 4 Version: 4.1.24 Platform: All OS/Version: All Status: NEW Severity:

DO NOT REPLY [Bug 16400] - Allow AccessLogValve to ignore (not log) requests for particular URIs

gzilla/show_bug.cgi?id=16400 Allow AccessLogValve to ignore (not log) requests for particular URIs --- Additional Comments From [EMAIL PROTECTED] 2003-01-24 17:44 --- Created an attachment (id=4540) A more readable diff, without indent-only changes (cvs diff -ub) -- To unsubscribe,

DO NOT REPLY [Bug 16400] - Allow AccessLogValve to ignore (not log) requests for particular URIs

gzilla/show_bug.cgi?id=16400 Allow AccessLogValve to ignore (not log) requests for particular URIs --- Additional Comments From [EMAIL PROTECTED] 2003-01-24 17:41 --- Created an attachment (id=4539) Patch diff (cvs diff -u) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> Fo

DO NOT REPLY [Bug 16400] New: - Allow AccessLogValve to ignore (not log) requests for particular URIs

gzilla/show_bug.cgi?id=16400 Allow AccessLogValve to ignore (not log) requests for particular URIs Summary: Allow AccessLogValve to ignore (not log) requests for particular URIs Product: Tomcat 4 Version: 4.1.20 Platform: All OS/V

DO NOT REPLY [Bug 16374] New: - Make access log filename date format configurable in AccessLogValve

gzilla/show_bug.cgi?id=16374 Make access log filename date format configurable in AccessLogValve Summary: Make access log filename date format configurable in AccessLogValve Product: Tomcat 4 Version: 4.1.20 Platform: All OS/Versio

Re: Tomcat "id" in AccessLogValve and Spread

You can declare your own custom pattern in AccessLogValve in server.xml. Then you can always hardcode your "id" into the pattern. -Tim Aditya wrote: I'm trying to consolidate the access logs for a whole bunch of Tomcats using Spread (www.spread.org) like I do with Apache. The ea

Re: Tomcat "id" in AccessLogValve and Spread

I would also like to add functionality to the AccessLogValve, and a subclass would be fine for my purposes, but currently, org.apache.catalina.valves.AccessLogValve is declared final, presumably for performance reasons. Is there any chance of changing that? Mike Shapira, Yoav wrote: Howdy

RE: Tomcat "id" in AccessLogValve and Spread

trivially. Perhaps it would be better to subclass AccessLogValve to add this functionality? Then you could contribute your class to the tomcat project and users of the normal AccessLogValve wouldn't need to know anything (or depend on) Spread. >somewhat figure out where it came from, but I

Tomcat "id" in AccessLogValve and Spread

that I am collecting access logs from multiple Tomcats in a single location, I need to be able to tell which Tomcat a log line came from. Since the AccessLogValve comes from inside a stanza, I can use %v to somewhat figure out where it came from, but I run into problems when I have multiple Tomcats loa

DO NOT REPLY [Bug 14724] - [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation

gzilla/show_bug.cgi?id=14724 [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 14724] - [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation

gzilla/show_bug.cgi?id=14724 [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation [EMAIL PROTECTED] changed: What|Removed |Added Priority

DO NOT REPLY [Bug 14724] - [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation

gzilla/show_bug.cgi?id=14724 [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 14724] - [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation

gzilla/show_bug.cgi?id=14724 [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation --- Additional Comments From [EMAIL PROTECTED] 2002-11-21 02:05 --- *** Bug 12145 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTEC

DO NOT REPLY [Bug 12145] - [PATCH] AccessLogValve - %{xxx}i implementation

gzilla/show_bug.cgi?id=12145 [PATCH] AccessLogValve - %{xxx}i implementation [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 14724] - [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation

gzilla/show_bug.cgi?id=14724 [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation --- Additional Comments From [EMAIL PROTECTED] 2002-11-21 02:04 --- Created an attachment (id=3907) patch file for AccessLogValve.java from cvs -- To unsubscribe, e-mail: <mail

DO NOT REPLY [Bug 14724] New: - [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation

gzilla/show_bug.cgi?id=14724 [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation Summary: [PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation Product: Tomcat 4 Version: Nightly Build Platfor

DO NOT REPLY [Bug 14281] - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... --- Additional Comments From [EMAIL PROTECTED] 2002-11-10 18:19 --- Yes, I think this makes sense. Good job finding the cause of the problem :) -- To unsubscribe, e-mail: <mailto:tomcat-d

DO NOT REPLY [Bug 14281] - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... --- Additional Comments From [EMAIL PROTECTED] 2002-11-10 11:56 --- I've sent two patch atachments to: org.apache.coyote.tomcat4.OutputBuffer.java org.apache.coyote.tomcat4.CoyoteRes

DO NOT REPLY [Bug 14281] - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... --- Additional Comments From [EMAIL PROTECTED] 2002-11-10 11:54 --- Created an attachment (id=3795) Changes on org.apache.coyote.tomcat4.Changes on org.apache.coyote.tomcat4.CoyoteResponse.

DO NOT REPLY [Bug 14281] - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... --- Additional Comments From [EMAIL PROTECTED] 2002-11-10 11:54 --- Created an attachment (id=3794) Changes on org.apache.coyote.tomcat4.OutputBuffer.java -- To unsubscribe, e-mail: <mai

DO NOT REPLY [Bug 14281] - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... --- Additional Comments From [EMAIL PROTECTED] 2002-11-10 02:08 --- I've found the root cause of the error (I think) at coyote classes. org.apache.coyote.tomcat4.CoyoteR

DO NOT REPLY [Bug 14281] - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED

DO NOT REPLY [Bug 14281] - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 14281] New: - AccessLogValve doesn't export BytesSent info from servlets...

gzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... Summary: AccessLogValve doesn't export BytesSent info from servlets... Product: Tomcat 4 Version: 4.1.12 Platform: PC O

DO NOT REPLY [Bug 12145] - [PATCH] AccessLogValve - %{xxx}i implementation

gzilla/show_bug.cgi?id=12145 [PATCH] AccessLogValve - %{xxx}i implementation --- Additional Comments From [EMAIL PROTECTED] 2002-09-10 12:16 --- Created an attachment (id=2988) used -u flag for cvs diff: [cvs diff -u AccessLogValve.java >AccessLogValve.diff2] -- To unsubscribe, e-mail:

DO NOT REPLY [Bug 12145] - [PATCH] AccessLogValve - %{xxx}i implementation

gzilla/show_bug.cgi?id=12145 [PATCH] AccessLogValve - %{xxx}i implementation --- Additional Comments From [EMAIL PROTECTED] 2002-08-29 00:00 --- Created an attachment (id=2864) cvs diff AccessLogValve.java >AccessLogValve.diff -- To unsubscribe, e-mail: <mailto:[EMAIL PRO

DO NOT REPLY [Bug 12145] New: - [PATCH] AccessLogValve - %{xxx}i implementation

gzilla/show_bug.cgi?id=12145 [PATCH] AccessLogValve - %{xxx}i implementation Summary: [PATCH] AccessLogValve - %{xxx}i implementation Product: Tomcat 4 Version: 4.1.9 Platform: All OS/Version: All Status: NEW Severity: Enhan

DO NOT REPLY [Bug 7554] - AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i

gzilla/show_bug.cgi?id=7554 AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

AccessLogValve

I was considering extending AccessLogValve to add the responsetime to the access log, but it looks like the class is declared final. Is there a reason why this is so? Is there a more appropriate logvalve that is designed to be extended? thanks in advance. peter -- To unsubscribe, e-mail

DO NOT REPLY [Bug 7554] - AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i

gzilla/show_bug.cgi?id=7554 AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED

DO NOT REPLY [Bug 7554] - AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i

gzilla/show_bug.cgi?id=7554 AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 7554] New: - AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i

gzilla/show_bug.cgi?id=7554 AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i Summary: AccessLogValve doesn't implement %{Referer}i and %{User- Agent}i Product: Tomcat 4 Version: 4.0.4 Beta 1 Platform: Other O

DO NOT REPLY [Bug 5319] - AccessLogValve does not resolve hostname

gzilla/show_bug.cgi?id=5319 AccessLogValve does not resolve hostname [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PRO

DO NOT REPLY [Bug 5319] - AccessLogValve does not resolve hostname

gzilla/show_bug.cgi?id=5319 AccessLogValve does not resolve hostname [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 5319] - AccessLogValve does not resolve hostname

gzilla/show_bug.cgi?id=5319 AccessLogValve does not resolve hostname --- Additional Comments From [EMAIL PROTECTED] 2001-12-12 12:38 --- As I already noted in this bug, InetAddress.getByName(request.getRemoteAddr()).getHostName() works correctly in the servlet that is invoked. therefo

DO NOT REPLY [Bug 5319] - AccessLogValve does not resolve hostname

gzilla/show_bug.cgi?id=5319 AccessLogValve does not resolve hostname --- Additional Comments From [EMAIL PROTECTED] 2001-12-12 12:20 --- Even if your TOmcat configuration is set up correctly, you will still get IP addresses instead of host names if your DNS environment is not set up cor

DO NOT REPLY [Bug 5319] - AccessLogValve does not resolve hostname

gzilla/show_bug.cgi?id=5319 AccessLogValve does not resolve hostname --- Additional Comments From [EMAIL PROTECTED] 2001-12-10 12:42 --- After looking through the source code and finding out that request.getRemoteHost () also does not return the hostname, I found bug 4180 which may be th

DO NOT REPLY [Bug 5319] New: - AccessLogValve does not resolve hostname

gzilla/show_bug.cgi?id=5319 AccessLogValve does not resolve hostname Summary: AccessLogValve does not resolve hostname Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version: Other Status: NEW Severity: Normal Pr

Re: AccessLogValve improved

on 5/6/01 4:58 AM, "Stefan Reich" <[EMAIL PROTECTED]> wrote: > Would you like to review my code (it's less than 10 lines) and maybe commit my > patch to CVS? Who can I send the file to? (I patched against 4.0 b3.) > > -Stefan -jon -- If you come f

AccessLogValve improved

Hi Tomcat developers,   I taught AccessLogValve how to display referer and user-agent. Now it can generate full-grown access logs that make traffic analyzers like Webalizer happy.   The new codes are %R (referer) and %g (user agent - %u, %u, %a and %A were taken). Use it like this to

Re: AccessLogUtil and minor patch to AccessLogValve

on 1/12/01 11:52 PM, "David Weinrich" <[EMAIL PROTECTED]> wrote: > In diving through the documentation I found for log4j, and hitting the > website I noticed...it is now part of the jakarta project (yay!). Seems like > this would be a (much much much) better idea than my mostly-untested syslog >

Re: AccessLogUtil and minor patch to AccessLogValve

David Weinrich wrote: > In diving through the documentation I found for log4j, and hitting the > website I noticed...it is now part of the jakarta project (yay!). Seems like > this would be a (much much much) better idea than my mostly-untested syslog > code for an addition to the logger classes,

Re: AccessLogUtil and minor patch to AccessLogValve

In diving through the documentation I found for log4j, and hitting the website I noticed...it is now part of the jakarta project (yay!). Seems like this would be a (much much much) better idea than my mostly-untested syslog code for an addition to the logger classes, any thoughts on this? David W

AccessLogUtil and minor patch to AccessLogValve

for JDBCAccessLog ). In addition I have some minimal syslog client code sitting around gathering dust, I know one or two people have requested syslog logs and access logs. If someone wants I can clean this code up and create a org.apache.catalina.logger.SyslogLogger class. One last note: while lo

Re: AccessLogValve Patch

In the message I just wrote: > > --- AccessLogValve.java Wed Jan 10 15:16:10 2001 > +++ AccessLogValve.java-new Wed Jan 10 15:15:50 2001 > @@ -61,6 +61,7 @@ > package org.apache.catalina.valves; > > > +import java.io.BufferedWriter; > import java.io.File; > import java.io.FileWriter;

AccessLogValve Patch

Hi guys. Here's another patch to the AccessLogValve. I noticed that since I changed it to perform better, it was creating log files named "localhost_access_log..txt". It was a simple bug that I have found and fixed (sorry about that). Plus, I made a few other very minor mod

Re: AccessLogValve performance fixes

--- Jason Brittain <[EMAIL PROTECTED]> wrote: > > Remy Maucherat wrote: > > > Quoting "Craig R. McClanahan" <[EMAIL PROTECTED]>: > > > >> Logging messages in some other environments -- and even Tomcat 3.x > IIRC > >> -- are > >> actually written out by a background thread, rather than the main

Re: AccessLogValve performance fixes

Jason Brittain wrote: > > It sounds like a good idea. While I was working on this valve I was > thinking > that it would be great to queue up the log messages for another thread, but > I first wanted to quickly get these lighter optimization changes into the > codebase. > Sounds like a reasonab

Re: AccessLogValve performance fixes

Remy Maucherat wrote: > Quoting "Craig R. McClanahan" <[EMAIL PROTECTED]>: > >> Logging messages in some other environments -- and even Tomcat 3.x IIRC >> -- are >> actually written out by a background thread, rather than the main >> request-processing thread (as it currently is with Catalina,

Re: AccessLogValve performance fixes

Quoting "Craig R. McClanahan" <[EMAIL PROTECTED]>: > Logging messages in some other environments -- and even Tomcat 3.x IIRC > -- are > actually written out by a background thread, rather than the main > request-processing thread (as it currently is with Catalina, or at least > it was > last time

Re: AccessLogValve performance fixes

Jason Brittain wrote: > Remy Maucherat wrote: > > >> Yep! That's a full 10 seconds slower than the new version, making > >> the new version about 44% faster. > > > > > > Great ! > > I'll commit the patch later today. > > > >> This test is single-threaded, but I think it still shows noticeable >

Re: AccessLogValve performance fixes

Remy Maucherat wrote: >> Yep! That's a full 10 seconds slower than the new version, making >> the new version about 44% faster. > > > Great ! > I'll commit the patch later today. > >> This test is single-threaded, but I think it still shows noticeable >> performance improvement. >> >> Somet

Re: AccessLogValve performance fixes

> Yep! That's a full 10 seconds slower than the new version, making > the new version about 44% faster. Great ! I'll commit the patch later today. > This test is single-threaded, but I think it still shows noticeable > performance improvement. > > Something else that I could do with this that I

AccessLogValve performance fixes

I've just completed some performance fixes to the AccessLogValve. My tests show that it's now more than 40% faster. I found that it was creating far more Date objects than it needed to, and formatting date strings too often as well. I've optimized most of that, which is what ac