tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 52688] New: Added ability to have access logs output to standard logging mechanism
Date Thu, 16 Feb 2012 21:40:18 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=52688

             Bug #: 52688
           Summary: Added ability to have access logs output to standard
                    logging mechanism
           Product: Tomcat 7
           Version: 7.0.25
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Catalina
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: markclaassenx@gmail.com
    Classification: Unclassified


Created attachment 28344
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=28344
Diff of AccessLogValve patch

The current AccessLogValve implementation uses a custom file writer instead of
the normal log mechanism.  There are circumstances where it would be nice to
have the power and flexibility of the standard logging capabilities.

This was briefly discussed in a email thread with subject 'AccessLogValve
enhancement' from 2.15.2012

Attached is a proposed patch to add this capability, however I think it is
still up for debate if this is a good enhancement.  This would be an option
that people wouldn't have to use.

I believe it will work for me and is hopefully generally useful (otherwise it
doesn't make a good enhancement and is just clutter.)   Earlier, I was trying
to see how to do this by searching on the web and I found several others asking
the same thing.  So, I think there are many others who at least think they want
this feature.

Issues:
* (Potential performance, as mentioned previously)
* "common" pattern for AccessLogValve includes timestamp, which is also often
included in log record headers.
* header messages (#VERSION, #FIELDS:, #SOFTWARE) won't repeat in log files,
and are not
  necessarily useful in the initial one. (#FIELD is null, presumably because
its attribute was later in my server.xml file.)

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message