[logback-dev] [JIRA] Created: (LBCORE-73) Add option to make <consolePlugin/> fail silently if no SocketServer is running

Paul Nyheim (JIRA) noreply-jira at qos.ch
Tue Nov 18 10:44:35 CET 2008

Add option to make <consolePlugin/> fail silently if no SocketServer is running

                 Key: LBCORE-73
                 URL: http://jira.qos.ch/browse/LBCORE-73
             Project: logback-core
          Issue Type: Improvement
          Components: Appender
    Affects Versions: 0.9.11
            Reporter: Paul Nyheim
            Assignee: Logback dev list
            Priority: Minor

For my JUnit tests, I have configured a logback-test.xml file with only a <consolePlugin/> entry. (debug=false) 
However, when I run the tests on the build-server, I get the following printed to System.out:

09:02:23,596 |-ERROR in ch.qos.logback.classic.net.SocketAppender[null] - Could not connect to remote logback server at [localhost]. We will try again later.
java.net.ConnectException: Connection refused: connect
       at java.net.ConnectException: Connection refused: connect
       at      at java.net.PlainSocketImpl.socketConnect(Native Method)
       at      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
       at      at

I realize that this message is part of logbacks internal status, however it would be nice to have the option to disable this message which pollutes the build-log on the build-server. Maybe by specifying an attribute like this: <consolePlugin silent="true"/> where the underlying Socketappender will be silent if it is not able to connect to the host and port.

I'll see if I can upload a patch later today.
Paul Nyheim

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list