[jira] [Commented] (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:comment-tabpanel=16434787#comment-16434787 ] ASF GitHub Bot commented on LOG4J2-2299: GitHub user cakofony opened a pull request:

[GitHub] logging-log4j2 pull request #164: [LOG4J2-2299] Mixed async loggers no longe...

GitHub user cakofony opened a pull request: https://github.com/apache/logging-log4j2/pull/164 [LOG4J2-2299] Mixed async loggers no longer forget parameter values Previously each AsyncLoggerConfig would individually enqueue an event on the async delegate disruptor. In practice

[jira] [Commented] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434795#comment-16434795 ] Carter Kozak commented on LOG4J2-2301: -- Alright, I've refactored AsyncLoggerConfig and managed to

[jira] [Created] (LOG4J2-2315) LevelRangeFilter min and max values are behaving opposit

JIGNESH S SHUKLA created LOG4J2-2315: Summary: LevelRangeFilter min and max values are behaving opposit Key: LOG4J2-2315 URL: https://issues.apache.org/jira/browse/LOG4J2-2315 Project: Log4j 2

[jira] [Work started] (LOG4J2-2301) gc-free mixed async loging loses parameter values after the first appender

[ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-2301 started by Carter Kozak. > gc-free mixed async loging loses parameter values after the first appender >