[
https://issues.apache.org/jira/browse/LOG4J2-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652649#comment-16652649
]
ASF GitHub Bot commented on LOG4J2-2475:
----------------------------------------
Github user remkop commented on the issue:
https://github.com/apache/logging-log4j2/pull/220
Good point that we cannot distinguish between parameter arrays created by
the user (which we shouldn’t reuse) and parameter arrays created by the
compiler because of a varargs invocation.
Would it be an idea to clone large (size greater than 10) parameter arrays?
(And use this cloned array in the reusable message.)
That would ensure we won’t modify user-specified arrays.
> Limit reusable event.clear parameter clearing to argsCount
> ----------------------------------------------------------
>
> Key: LOG4J2-2475
> URL: https://issues.apache.org/jira/browse/LOG4J2-2475
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
>
> Larger parameter arrays may make their way into log4j when passed into the
> logger directly. These may take longer to clear, despite only containing one
> or two parameters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
