[
https://issues.apache.org/jira/browse/LOG4J2-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531780#comment-16531780
]
ASF subversion and git services commented on LOG4J2-2312:
---------------------------------------------------------
Commit 34cc745705b0c33d79ef326032edf9cb212fc26f in logging-log4j2's branch
refs/heads/master from [~ckozak]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=34cc745 ]
LOG4J2-2312 LOG4J2-2341 Fix jackson layout with async loggers
AsyncLoggerContextSelector RingBufferLogEvents were not properly
handled by the jackson layout. Currently the jackson layout
implementation requires Log4jLogEvent instances, so we must
convert all other LogEvent implementations into these.
This closes #187
> Using async appender with json layout causes only the message to be written
> ---------------------------------------------------------------------------
>
> Key: LOG4J2-2312
> URL: https://issues.apache.org/jira/browse/LOG4J2-2312
> Project: Log4j 2
> Issue Type: Bug
> Reporter: David Knapp
> Assignee: Carter Kozak
> Priority: Major
> Attachments: async_trace.txt, synchronous_trace.txt
>
>
> When using the async appender combined with the JsonLayout, you only get the
> results of the message being written to the appender.
>
> I took a look at it seems like this is because RingBufferLogEvent implements
> ReusableMessage which is where jackson gets the MessageSerializer, whereas
> the non async LogEvent doesn't, so it gets the BeanSerializer
> Attached are traces, both of which originating from the
> MessageSerializer.serialize method
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
