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

["Carter Kozak (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423340#comment-16423340 ] 

Carter Kozak edited comment on LOG4J2-2301 at 4/3/18 3:48 AM:
--------------------------------------------------------------

Perfect, will do!

 

Edit: Holding off just a bit for LOG4J-2299, commit for that issue provides utilities I'd like to use in this test


was (Author: ckozak):
Perfect, will do!

> gc-free mixed async loging loses parameter values after the first appender
> --------------------------------------------------------------------------
>
>                 Key: LOG4J2-2301
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2301
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.11.0
>            Reporter: Carter Kozak
>            Priority: Major
>
> When gc-free logging is used with mixed synchronous/asynchronous loggers, parameter values are replaced with "null" after the first AsyncLoggerConfig.
> The message format is still present, as well as the parameter count, however all values are nulls.
> It appears that Log4jEventWrapperHandler.onEvent invokes MutableLogEvent.clear, which nulls out the parameter array.
> I have constructed a failing test (which I need to clean up and deduplicate some code from the fix for LOG4J2-2299):
> https://github.com/cakofony/logging-log4j2/commit/b9c03f5c6881bfe778f8e2d75d046ce6e021c4f1



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