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 Douglas Kozak (JIRA)" <ji...@apache.org> on 2018/03/30 19:37:00 UTC

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

Carter Douglas Kozak created LOG4J2-2299:
--------------------------------------------

             Summary: 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 Douglas Kozak


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)