[logback-dev] [JIRA] Commented: (LBCLASSIC-193) SyslogAppender quits after a while

[Ralph Goers (JIRA)]

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

Ralph Goers commented on LBCLASSIC-193:
---------------------------------------

Google tells me that a system setting is causing the Message too long exception. Unfortunately, when SyslogAppenderBase encounters an IOException it calls stop(), which disables the Appender.  Unfortunately, SyslogAppenderBase doesn't provide any way to change this behavior.

> SyslogAppender quits after a while
> ----------------------------------
>
>                 Key: LBCLASSIC-193
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-193
>             Project: logback-classic
>          Issue Type: Bug
>          Components: appender
>    Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19
>         Environment: At least Debian Etch with JDK5
>            Reporter: Ingo Siebert
>            Assignee: Logback dev list
>            Priority: Critical
>
> I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine.
> But after several days and weeks, more and more servers  doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs.
> I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57.
> In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies.  
> If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. 
> The SysLog-Appender is useless for me until this bug is fixed.

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