Summary: | Reduce first connection failure severity in SocketAppender | ||
---|---|---|---|
Product: | Log4j - Now in Jira | Reporter: | Christian Stein <sormuras> |
Component: | Appender | Assignee: | log4j-dev <log4j-dev> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 1.2 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Christian Stein
2004-05-26 13:57:57 UTC
1.2.12 candiate 1.2.15 candidate Note: In log4j 1.2 branch, there is currently no 'error' level internal logging. To minimize the amount of change, I'm proposing to make this a warn level internal event, and remove the stack trace. I plan to commit the following diff: Index: src/java/org/apache/log4j/net/SocketAppender.java =================================================================== --- src/java/org/apache/log4j/net/SocketAppender.java (revision 531299) +++ src/java/org/apache/log4j/net/SocketAppender.java (working copy) @@ -211,7 +211,7 @@ msg += " We will try again later."; fireConnector(); // fire the connector thread } - LogLog.error(msg, e); + LogLog.warn(msg); } } If I had been more caffeinated I would have seen there really is a LogLog.error(String) method, which I'm using instead. |