[LOG4J2-1271] ParameterizedMessage optimization

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 2.6
• Component/s: API
• Epic Link: GC-free
• Assignee: Remko Popma
• Reporter: Remko Popma
• Created: 13/Feb/16 05:05
• Updated: 23/Feb/16 17:57
• Resolved: 23/Feb/16 17:57

Description

ParameterizedMessage creates unnecessary objects and does other unnecessary work in its constructor.
On the other hand, it does not create the full formatted string it will eventually need to return from getFormattedMessage().

I propose the following changes:

• Don't call argumentsToStrings in the constructor. Converting the parameter Object[] array to a String[] array should only be done when necessary: when this ParameterizedMessage is serialized.
• Don't copy the parameter Object[] array to a new array. Instead clone the array when the getParameters() method is called.
• In the constructor, build the fully formatted message. This combines the work done by formatStringArgs(String, String[]) and argumentsToStrings(Object[]) and avoids the issue mentioned in LOG4J2-763.

Issue Links

• relates to: LOG4J2-1293 GC-friendly Message API enhancement