[ http://jira.qos.ch/browse/LBCORE-228?page=com.atlassian.jira.plugin.system.i... ] Pasi Eronen commented on LBCORE-228: ------------------------------------ Many Linux distros seem to use Rsyslog, where 65000 bytes works just fine (if you set $MaxMessageSize 65000), at least over the localhost interface (where MTU is typically large, so the message isn't split to dozens of fragments). (And RFC 3164 has been obsoleted by RFC 5424/5425, which recommend supporting much longer messages than 1024 bytes).
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