[
https://issues.apache.org/jira/browse/LOG4J2-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831347#comment-15831347
]
Alexandru Ionita commented on LOG4J2-1795:
------------------------------------------
I forgot to take out the test {{expect Exception}}, so that the test that
demonstrates the issue wasn't failing.
https://github.com/nucatus/LogEventSerializationPOC/commit/bf76df3d469c97d6fb457922d7abe3edc5d0523c#diff-a0fdeb2676d703f5d5ddaecfdd451037
Another issue we observed is that using the serialization mechanism you have in
that unit test will omit the {{ParameterizedMessage}} variables in the
deserialized object.
Please check again. Thanks.
> LogEvent serialization deserialization
> --------------------------------------
>
> Key: LOG4J2-1795
> URL: https://issues.apache.org/jira/browse/LOG4J2-1795
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.7
> Reporter: Alexandru Ionita
> Labels: serializable
>
> Deserialization of a LogEvent that has been serialized with the
> Log4jLogEvent.serialize method fails after the serialized object went through
> a byte stream.
> Here is a test that demonstrates the issue:
> https://github.com/nucatus/LogEventSerializationPOC
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
