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 24233] New: - Loggers broken?
Date Wed, 29 Oct 2003 22:57:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24233

Loggers broken?

           Summary: Loggers broken?
           Product: Tomcat 5
           Version: 5.0.14
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: chris.halstead@delta.com


In TC 5.0.12 I was able to set up per-engine and per-context loggers by nesting
<Logger> elements.  This seems to be broken in 5.0.13 and 5.0.14.

To wit, the out-of-the-box installation of Tomcat 5.0.12 creates a per-engine
log (catalina_log) and a per-host log (localhost_log), as well as a log for the
'admin' context (localhost_admin).  In the default 5.0.13 and 5.0.14 install
these Loggers are still defined, but only the localhost_log works.  I am also
unable to create per-context Loggers in 5.0.13 or 5.0.14 by nesting <Logger>
elements either within a server.xml-based <Context> or within a context
descriptor file.

This behaviour is consistent across Solaris, Windows and Linux, and across both
the Sun and IBM VMs.

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


Mime
View raw message