[
https://issues.apache.org/jira/browse/LOG4J2-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531548#comment-16531548
]
ASF GitHub Bot commented on LOG4J2-2312:
----------------------------------------
Github user cakofony commented on a diff in the pull request:
https://github.com/apache/logging-log4j2/pull/187#discussion_r199848400
--- Diff: log4j-layout-jackson-json/pom.xml ---
@@ -55,6 +55,11 @@
<type>test-jar</type>
<version>${project.version}</version>
</dependency>
+ <dependency>
+ <groupId>com.lmax</groupId>
+ <artifactId>disruptor</artifactId>
+ <scope>test</scope>
+ </dependency>
--- End diff --
Required to construct a RingBufferLogEvent
> 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)
