[
https://issues.apache.org/jira/browse/LOG4J2-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423451#comment-16423451
]
Carter Kozak commented on LOG4J2-2299:
--------------------------------------
Implementation of the proposal for the memento change:
[https://github.com/cakofony/logging-log4j2/commit/e12cd25b741b424485d7aef9ff78a1bc5aaaa883]
Would it be preferable if I filed a separate ticket to track that?
> 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)
