[
https://issues.apache.org/jira/browse/LOG4J2-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350907#comment-15350907
]
Mikael Ståldal commented on LOG4J2-1115:
----------------------------------------
I think that LOG4J2-1010 will make this issue unnecessary.
> Allow fine-grained control over which properties are passed to child threads.
> -----------------------------------------------------------------------------
>
> Key: LOG4J2-1115
> URL: https://issues.apache.org/jira/browse/LOG4J2-1115
> Project: Log4j 2
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.3
> Reporter: Ralph Goers
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
