You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2012/05/01 06:25:48 UTC
[jira] [Resolved] (LOG4J2-21) LoggingEvent message lost on
serialization
[ https://issues.apache.org/jira/browse/LOG4J2-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-21.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha1
Assignee: Ralph Goers
This is an inherent part of the Log4j 2 architecture.
> LoggingEvent message lost on serialization
> ------------------------------------------
>
> Key: LOG4J2-21
> URL: https://issues.apache.org/jira/browse/LOG4J2-21
> Project: Log4j 2
> Issue Type: Wish
> Components: Appenders
> Reporter: Curt Arnold
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> log4j bug 42023 complained that the LoggingEvent serialization did not attempt to serialize the message object, but only serialized the rendered message. Whatever serialized forms are supported in log4j 2.0 should provide the option to transmit a serialized form of the message object.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org