ConnectException when using <consolePlugin/>

Hi. 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 java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) 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. Regards, Paul Nyheim

Hello Paul, In order to avoid that this falls through the cracks, could you please enter a jira issue. Thank you, Paul Nyheim wrote:
Hi. 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 java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
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.
Regards, Paul Nyheim
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

Sure thing. I just wanted to do a sanity check first - that this was not already possible. I'll create the Jira issue asap. On Tue, Nov 18, 2008 at 10:29 AM, Ceki Gulcu <listid@qos.ch> wrote:
Hello Paul,
In order to avoid that this falls through the cracks, could you please enter a jira issue.
Thank you,
Paul Nyheim wrote:
Hi. 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 java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
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.
Regards, Paul Nyheim
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user

Issue created: http://jira.qos.ch/browse/LBCORE-73 I'll see if I can make a patch later today. On Tue, Nov 18, 2008 at 10:31 AM, Paul Nyheim <hurragutt@gmail.com> wrote:
Sure thing. I just wanted to do a sanity check first - that this was not already possible.
I'll create the Jira issue asap.
On Tue, Nov 18, 2008 at 10:29 AM, Ceki Gulcu <listid@qos.ch> wrote:
Hello Paul,
In order to avoid that this falls through the cracks, could you please enter a jira issue.
Thank you,
Paul Nyheim wrote:
Hi. 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 java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
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.
Regards, Paul Nyheim
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
participants (2)
-
Ceki Gulcu
-
Paul Nyheim