DO NOT REPLY [Bug 29227] New: - Reduce first connection failure severity in SocketAppender

[bu...@apache.org]

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

Reduce first connection failure severity in SocketAppender

           Summary: Reduce first connection failure severity in
                    SocketAppender
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Appender
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: sormuras@web.de


Rather than the printing the mesage via LogLog.error(...)

229    /**
230     * Rather than log an ugly stack trace, output the msg
231     */
232    LogLog.error(msg + "(" + e.getMessage() + ")");

use 

232    LogLog.info(msg + "(" + e.getMessage() + ")");

or

232    LogLog.debug(msg + "(" + e.getMessage() + ")");

...just like done in the SocketAppender$Connector class.

IMHO, it is a common fact, that the log server is not reachable at the time the 
logging application starts. The reconnection connector takes care of this in a 
"silent" manner. If one was interested in log4j verbosity, use LogLog.
setInternalDebugging(true). The same "silent" policy should be applied to the 
first connection trial initiated by activateOptions() method.

My current work around is calling LogLog.setQuietMode(true) before the log4j 
initialization procedure -- which mutes all other interesting messages as well.

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