You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Robert Middleton (Jira)" <lo...@logging.apache.org> on 2021/02/16 02:11:00 UTC
[jira] [Resolved] (LOGCXX-324) exception on logging long message to
syslog
[ https://issues.apache.org/jira/browse/LOGCXX-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Middleton resolved LOGCXX-324.
-------------------------------------
Assignee: Robert Middleton (was: Curt Arnold)
Resolution: Fixed
This is now believed to be fixed with PR #46.
> exception on logging long message to syslog
> -------------------------------------------
>
> Key: LOGCXX-324
> URL: https://issues.apache.org/jira/browse/LOGCXX-324
> Project: Log4cxx
> Issue Type: Bug
> Components: Appender
> Affects Versions: 0.10.0
> Environment: Linux
> Reporter: Ben Hockley
> Assignee: Robert Middleton
> Priority: Major
>
> An exception is raised by log4cxx when a very large message is logged using the SyslogAppender/SyslogWriter (other appenders/writers appear to "work" perfectly with large messages).
> The exception occurs if the message in question is too large to fit inside a UDP packet (the syslog protocol uses UDP).
> It would be better to split big messages up before sending them over the syslog protocol as per this similar log4j issue/fix - https://issues.apache.org/bugzilla/show_bug.cgi?id=42087 - rather than forcing log4cxx clients to restructure their program logic in order to avoid (or recover from) from this kind of rare logging exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)