[LOG4J2-2253] Reusable messages missing a garbage free parameter accessor

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.11.0
• Assignee: Remko Popma
• Reporter: Carter Kozak
• Created: 16/Feb/18 19:52
• Updated: 27/Feb/18 10:03
• Resolved: 26/Feb/18 10:52

Description

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

Issue Links

• links to: GitHub Pull Request #150