[
https://issues.apache.org/jira/browse/LOGCXX-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173201#comment-17173201
]
Thorsten Schöning commented on LOGCXX-455:
------------------------------------------
Added a [PR|https://github.com/apache/logging-log4cxx/pull/33] to fix this by
really doing what the report wanted, making things quiet. Doesn't make too much
sense to me to introduce new config options are similar.
> 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
(v8.3.4#803005)
