[logback-dev] [JIRA] Commented: (LBCORE-228) Syslog messages over 64K are discarded

Ralph Goers (JIRA) noreply-jira at qos.ch
Tue Oct 25 15:40:13 CEST 2011

    [ http://jira.qos.ch/browse/LBCORE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12227#action_12227 ] 

Ralph Goers commented on LBCORE-228:

Yes, I'm well aware of RFC 5424 - you can reference the issue(s) I opened with Logback and SLF4J quite a while ago to get them supported.  Logback doesn't support it directly and the message format of the two isn't quite compatible. SyslogAppender is designed to support only RFC 3164, which is still the dominant format used.

> Syslog messages over 64K are discarded
> --------------------------------------
>                 Key: LBCORE-228
>                 URL: http://jira.qos.ch/browse/LBCORE-228
>             Project: logback-core
>          Issue Type: Bug
>          Components: Appender
>    Affects Versions: 0.9.30
>            Reporter: Pasi Eronen
>            Assignee: Logback dev list
> SyslogAppenderBase truncates very long messages to 256k, which is not very useful limit, since SyslogOutputStream supports only UDP, which has maximum message size of 64k. Messages over 64k result in "java.io.IOException: Message too long" (from DatagramSocket.send, called from SyslogOutputStream.flush), but this exception is visible only in logger context status...
> Proposed fix: truncate long messages instead of discarding them. More specifically, change MSG_SIZE_LIMIT in SyslogAppenderBase to 65000.

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