[LOG4J2-1611] Improve performance of ThreadContextDataInjector.ForDefaultThreadContextMap

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.7
• Component/s: Core
• Assignee: Remko Popma
• Reporter: Remko Popma
• Created: 23/Sep/16 13:57
• Updated: 29/Jun/17 01:39
• Resolved: 25/Sep/16 00:40

Description

Current implementation of ThreadContextDataInjector.ForDefaultThreadContextMap::injectContextData always copies all elements from the ThreadContext into the reused StringMap of the LogEvent.

Since the DefaultThreadContextMap is used in web applications (when non-JDK thread-locals are not available and Log4j is not garbage-free), we don't need to worry about creating additional objects. We can speed up the injectContextData method by wrapping the context data Map<String, String> in a decorator object that implements the StringMap interface.

Issue Links

• is superceded by: LOG4J2-1607 Improve performance of SortedArrayStringMap data structure