[logback-dev] [JIRA] Commented: (LBCLASSIC-156) SocketAppender is reporting an WARN if connection could not be established.

Ceki Gulcu (JIRA) noreply-jira at qos.ch
Wed Feb 24 09:32:16 CET 2010

    [ http://jira.qos.ch/browse/LBCLASSIC-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11561#action_11561 ] 

Ceki Gulcu commented on LBCLASSIC-156:

Hi Joern, I'll look into it.

> SocketAppender is reporting an WARN if connection could not be established.
> ---------------------------------------------------------------------------
>                 Key: LBCLASSIC-156
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-156
>             Project: logback-classic
>          Issue Type: Improvement
>          Components: appender
>    Affects Versions: 0.917
>         Environment: java version "1.6.0_15"
> Java(TM) SE Runtime Environment (build 1.6.0_15-b03-226)
> Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-92, mixed mode)
>            Reporter: Joern Huxhorn
>            Assignee: Ceki Gulcu
> This is a followup to LBCLASSIC-143 which changed the message from ERROR to WARN.
> The WARN message still results in a dump of the logging status messages.
> This means that a whole bunch of text is printed to the console whenever Lilith is started - and it looks quite broken due to the stacktrace.
> So there are two possible solutions for this problem:
> a) the status is only printed in case of an ERROR
> b) SocketAppender considers this as an INFO instead of a WARN.
> I think b) would be reasonable. Other WARNs are much more important, like duplicate logback.xml.
> Lilith is only an example, btw.
> We routinely add SocketAppender[localhost] to our console applications. In case of trouble one can simply start Lilith and check the logs that way instead of reading them on the console.
> The default use-case is executing the app without Lilith, though, so we get the logback status messages on every start - which is quite noisy and annoying.

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