You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Carter Kozak (JIRA)" <ji...@apache.org> on 2018/07/03 19:38:00 UTC

[jira] [Resolved] (LOG4J2-2312) Using async appender with json layout causes only the message to be written

     [ https://issues.apache.org/jira/browse/LOG4J2-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carter Kozak resolved LOG4J2-2312.
----------------------------------
    Resolution: Fixed

This is fixed on master and the release-2.x branches. I have reproduced the failure with a unit test and fixed it.

> 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
>             Fix For: 3.0.0, 2.11.1
>
>         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)