You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2018/02/26 10:53:00 UTC

[jira] [Resolved] (LOG4J2-2253) Reusable messages missing a garbage free parameter accessor

     [ https://issues.apache.org/jira/browse/LOG4J2-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remko Popma resolved LOG4J2-2253.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.11.0

Merged into master and the release-2.x branch.
Thanks for the contribution!

Please verify and close this ticket.

> Reusable messages missing a garbage free parameter accessor
> -----------------------------------------------------------
>
>                 Key: LOG4J2-2253
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2253
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: Carter Douglas Kozak
>            Assignee: Remko Popma
>            Priority: Major
>             Fix For: 2.11.0
>
>
> I have a layout which iterates through message parameters, however Message.getParameters causes allocation on many implementations.
> It appears that ReusableMessage.swapParameters is supposed to fill this gap, however some messages types do allocation when this is invoked (see ReusableParameterizedMessage) which isn't helpful for access on a single thread where we don't want to take ownership of values.
> I've put together a proposal for an accessor similar to MapMessage:
> https://github.com/apache/logging-log4j2/pull/150



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