DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=20380.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32714.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/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: Catalina
/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
Status: NEW
/show_bug.cgi?id=32135
AccessLogValve directory attribute ignores leading slash
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=20380
AccessLogValve incorrectly calculates timezone
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED
/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: Other
/show_bug.cgi?id=26171
NullPointerException in AccessLogValve
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
://nagoya.apache.org/bugzilla/show_bug.cgi?id=26171
NullPointerException in AccessLogValve
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=20380
AccessLogValve incorrectly calculates timezone
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
/show_bug.cgi?id=16374
Make access log filename date format configurable in AccessLogValve
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
/show_bug.cgi?id=16400
Allow AccessLogValve to ignore (not log) requests for particular URIs
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
/show_bug.cgi?id=14281
AccessLogValve doesn't export BytesSent info from servlets...
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
/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: Normal
/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/Version: All
/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]
For additional
/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, e-mail: mailto
/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/Version: All
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 Host/ stanza, I can use %v to
somewhat figure out where it came from, but I run into problems when I have
multiple Tomcats load-balanced
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 run into problems when I
have
multiple Tomcats
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
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 easiest way to do
/show_bug.cgi?id=14724
[PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation
[EMAIL PROTECTED] changed:
What|Removed |Added
CC
/show_bug.cgi?id=14724
[PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation
[EMAIL PROTECTED] changed:
What|Removed |Added
Priority|Other
/show_bug.cgi?id=14724
[PATCH] AccessLogValve - %{xxx}i implementation AND disable log rotation
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
/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
Platform: All
OS
/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: mailto:[EMAIL PROTECTED
/show_bug.cgi?id=12145
[PATCH] AccessLogValve - %{xxx}i implementation
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/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 PROTECTED
/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.java
/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.CoyoteResponse.java
Ciao.
Please
/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-dev-unsubscribe
/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.CoyoteResponse calls
/show_bug.cgi?id=14281
AccessLogValve doesn't export BytesSent info from servlets...
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=14281
AccessLogValve doesn't export BytesSent info from servlets...
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
/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
OS/Version: Linux
/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: mailto
/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: Enhancement
/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 PROTECTED]
For additional
/show_bug.cgi?id=7554
AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
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
/show_bug.cgi?id=7554
AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=7554
AccessLogValve doesn't implement %{Referer}i and %{User-Agent}i
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
/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
OS/Version: Other
/show_bug.cgi?id=5319
AccessLogValve does not resolve hostname
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED
/show_bug.cgi?id=5319
AccessLogValve does not resolve hostname
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
/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 correctly.
Can
/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.
therefore the DNS
/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 the same
/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
Priority
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
code
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
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;
import
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
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.
Something else that I
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 I
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 reasonable
57 matches
Mail list logo
