You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Robert Middleton (Jira)" <lo...@logging.apache.org> on 2020/08/07 22:09:00 UTC

[jira] [Resolved] (LOGCXX-455) LogLog::setQuietMode(true) does not suppress exception reporting

     [ https://issues.apache.org/jira/browse/LOGCXX-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Middleton resolved LOGCXX-455.
-------------------------------------
    Resolution: Fixed

> 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)