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/03/30 21:59:00 UTC

[jira] [Work started] (LOG4J2-2299) Using "asyncLogger" with AsyncLoggerContextSelector loses some event data

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

Work on LOG4J2-2299 started by Carter Kozak.
--------------------------------------------
> Using "asyncLogger" with AsyncLoggerContextSelector loses some event data
> -------------------------------------------------------------------------
>
>                 Key: LOG4J2-2299
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2299
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.11.0
>            Reporter: Carter Kozak
>            Assignee: Carter Kozak
>            Priority: Major
>
> Using mixed style "asyncLogger" definitions when AsyncLoggerContextSelector is selected and reusable messages are enabled causes parameterized message data to be lost (Guessing we memento the message handing it off between disruptors).
> Proposal:
> Would it be objectionable to parse AsyncLoggerConfigs as standard LoggerConfig when global async mode is enabled?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)