[
https://issues.apache.org/jira/browse/LOG4J2-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185522#comment-14185522
]
Ralph Goers commented on LOG4J2-886:
------------------------------------
The SerializedLayout is a special case since the events are being serialized to
be sent to a remote system. One would never expect the ConsoleAppender to use
the SerializedLayout.
There are tools, such as Lillith - http://lilith.huxhorn.de/ - that allow
events to be sent to a generic log reporting tool. Since ThrowableProxy is a
Log4j class it should always be able to be deserialized. But if that tool does
not have the Class object for the actual exception that was thrown it will not
be able to deserialize it, but it will still have access to all the information
about the exception and the event via the getThrownProxy method.
> Not serializing the exception or ThreadContext (MDC)
> ------------------------------------------------------
>
> Key: LOG4J2-886
> URL: https://issues.apache.org/jira/browse/LOG4J2-886
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders, Layouts
> Affects Versions: 2.1
> Reporter: Mark Celano
>
> Not serializing the exception or ThreadContext (MDC) into the serialized
> LogEvent object when using the SerializedLayout for the Socket appender.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
