[LOG4J2-1115] Allow fine-grained control over which properties are passed to child threads.

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.3
• Component/s: Core
• Assignee: Unassigned
• Reporter: Ralph Goers
• Created: 09/Sep/15 20:52
• Updated: 27/Jun/16 12:23

Description

http://jira.qos.ch/browse/LOGBACK-624 contains the following comment; "My suggestion is that the user should be able to plug in a callback object in the Logback config indicating which keys should be propagated to child threads. This could be PropagateAll (legacy behavior), PropagateNone, PropagateRegex. I would suggest that the default should become PropagateNone, for the reasons I describe above, but making it configurable would probably make everybody happy and prevent more people from forking Logback (as my company has done, privately)."

Log4j current defaults the ThreadContextMap to use a regular ThreadLocal. If the user configures a property then an InheritableThreadLocal will be used. This proposal is to provide finer grained control over what properties are shared with child threads.

Issue Links

• is superceded by: LOG4J2-1010 Injectable context properties