[
https://issues.apache.org/jira/browse/LOG4J2-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646529#comment-16646529
]
ASF GitHub Bot commented on LOG4J2-2475:
----------------------------------------
GitHub user cakofony opened a pull request:
https://github.com/apache/logging-log4j2/pull/218
[LOG4J2-2475] More efficient parameter reset for reusable messages
Pushing to GH for feedback.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cakofony/logging-log4j2 parameter_clearing
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/218.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #218
----
commit d3c587ce3dcf107a4bc3ad66c0c926e662d0c63d
Author: Carter Kozak <ckozak@...>
Date: 2018-10-11T11:04:50Z
[LOG4J2-2475] More efficient parameter reset for reusable messages
----
> 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)
