logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28692] New: - non-configured log4j defaults could be better
Date Thu, 29 Apr 2004 19:09:11 GMT
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=28692>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28692

non-configured log4j defaults could be better

           Summary: non-configured log4j defaults could be better
           Product: Log4j
           Version: unspecified
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Other
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: bill-apache@carpenter.org


If log4j has no configuration, then the default Default DEFAULT is DEBUG level 
for the root logger.  Even though there are no appenders, this leads to 
inefficient behavior for logging applications.  They may do expensive 
calculations under the very reasonable assumption that things wouldn't be set to 
DEBUG level unless someone were interested in DEBUG logging.

I don't know what the best correction would be, but in my environment I change 
this to ERROR level.  This at least reduces the potentially enormous performance 
impact.

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


Mime
View raw message