You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2004/05/13 21:39:10 UTC

DO NOT REPLY [Bug 28962] New: - Suggest inserting CRITICAL error level in Level.java

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=28962>.
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=28962

Suggest inserting CRITICAL error level in Level.java

           Summary: Suggest inserting CRITICAL error level in Level.java
           Product: Log4j
           Version: 1.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Other
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: jonl@muppetlabs.com


a CRITICAL error is not FATAL, but it is worse than a regular ERROR because it
indicates that FATALity may be imminent.  CRITICAL errors might typically page
someone.  i think it would be worthwhile to add this extra granularity to
non-fatal errors.

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