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

Carter Kozak closed LOG4J2-2299.
--------------------------------
       Resolution: Duplicate
    Fix Version/s: 3.0.0

LOG4J2-2307 improved message mementos, fixing the data loss portion of this 
ticket. There's still a bit of allocation to create mementos, but I don't like 
the AsyncLoggerConfig factory method returning an object that isn't an 
AsyncLoggerConfig.

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

Reply via email to