[
https://issues.apache.org/jira/browse/LOGCXX-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546068#comment-14546068
]
Thorsten Schöning commented on LOGCXX-455:
------------------------------------------
This happens in loglog.cpp in all functions, debug, warn an error. May it be
that exceptions are treated special for a specific reason? I tend to agree that
"quiet" should mean "quiet" and exceptions ignored as well, but... If this gets
changed, I would suggest moving the check for "quietMode" directly into the two
emit methods, looks easier to maintain and more what one wants if quietMode is
set.
> LogLog::setQuietMode(true) does not suppress exception reporting
> ----------------------------------------------------------------
>
> Key: LOGCXX-455
> URL: https://issues.apache.org/jira/browse/LOGCXX-455
> Project: Log4cxx
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Bruce DeFrang
> Priority: Trivial
>
> LogLog::setQuietMode(true) suppresses error reporting but not exceptions
> associated with the errors.
> I discovered this while working with a configuration that uses
> org.org.apache.log4j.net.SocketAppender. If there is no log4j consumer
> running for the socket, log4cxx was reporting the following using loglog:
> log4cxx: Could not connect to remote log4cxx server at [server-name]. We will
> try again later.
> log4cxx: IO Exception : status code = 730061
> I used LogLog::setQuietMode(true) to suppress this, but the exception was
> still reported without the error text:
> log4cxx: IO Exception : status code = 730061
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
