|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Log4j 2 is doing something similar in the Map<String, String> part of their ThreadContext, using ThreadLocal by default but providing the ability to configure the use of InheritableThreadLocal if desired.
The related issue is LOG4J2-479 - Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful.
It was fixed during the rc-phase of 2.0.