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

Ralph Goers (JIRA) noreply-jira at qos.ch
Mon Oct 24 22:01:12 CEST 2011

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

Ralph Goers commented on LBCORE-228:

http://tools.ietf.org/html/rfc3164 says the maximum length of a syslog message is 1024 bytes. To be compliant the appender should be truncating messages to that length. Consider yourself lucky if anything over that length works.

> 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