View | Details | Raw Unified | Return to bug 55215
Collapse All | Expand All

(-)webapps/docs/config/valve.xml (-12 / +21 lines)
Lines 57-69 Link Here
57
57
58
  <subsection name="Introduction">
58
  <subsection name="Introduction">
59
59
60
    <p>The <strong>Access Log Valve</strong> creates log files in the same
60
    <p>The <strong>Access Log Valve</strong> creates log files in the
61
    format as those created by standard web servers.  These logs can later
61
    same format as those created by standard web servers.  These logs
62
    be analyzed by standard log analysis tools to track page hit counts,
62
    can later be analyzed by standard log analysis tools to track page
63
    user session activity, and so on.  The files produces by this <code>Valve</code>
63
    hit counts, user session activity, and so on.  This <code>Valve</code>
64
    are rolled over nightly at midnight.  This <code>Valve</code>
64
    uses self-contained logic to write its log files, which can be
65
    may be associated with any Catalina container (<code>Context</code>,
65
    automatically rolled over at midnight each day.  (The essential
66
    <code>Host</code>, or <code>Engine</code>), and
66
    requirement for access logging is to handle a large continuous
67
    stream of data with low overhead. This <code>Valve</code> does not
68
    use Apache Commons Logging, thus avoiding additional overhead and
69
    potentially complex configuration).</p>
70
71
    <p>This <code>Valve</code> may be associated with any Catalina container
72
    (<code>Context</code>, <code>Host</code>, or <code>Engine</code>), and
67
    will record ALL requests processed by that container.</p>
73
    will record ALL requests processed by that container.</p>
68
74
69
    <p>Some requests may be handled by Tomcat before they are passed to a
75
    <p>Some requests may be handled by Tomcat before they are passed to a
Lines 339-350 Link Here
339
345
340
  <subsection name="Introduction">
346
  <subsection name="Introduction">
341
347
342
    <p>The <strong>Extended Access Log Valve</strong> is a variant of
348
    <p>The <strong>Extended Access Log Valve</strong> extends the
343
    the Access Log Valve. It is not a real extension of the standard
349
    <a href="#Access_Log_Valve">Access Log Valve</a> class, and so
344
    Access Log valve, instead it supports the so-called
350
    uses the same self-contained logging logic.  This means it
351
    implements many of the same file handling attributes.  The main
352
    difference to the standard <code>AccessLogValve</code> is that
353
    <code>ExtendedAccessLogValve</code> creates log files which
354
    conform to the the Working Draft for the
345
    <a href="http://www.w3.org/TR/WD-logfile.html">Extended Log File Format</a>
355
    <a href="http://www.w3.org/TR/WD-logfile.html">Extended Log File Format</a>
346
    defined by the W3C. The main difference to the standard
356
    defined by the W3C.</p>
347
    <code>AccessLogValve</code> are the supported pattern values.</p>
348
357
349
  </subsection>
358
  </subsection>
350
359

Return to bug 55215