[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399011#comment-15399011
]
Remko Popma commented on LOG4J2-1010:
-------------------------------------
About avoiding interaction with ThreadContext, note that
[ThreadContextMapFilter|https://logging.apache.org/log4j/2.0/log4j-core/xref/org/apache/logging/log4j/core/filter/ThreadContextMapFilter.html]
and
[ContextMapLookup|https://logging.apache.org/log4j/2.0/log4j-core/xref/org/apache/logging/log4j/core/lookup/ContextMapLookup.html]
get values from ThreadContext, but that is fine since that is the "contract"
of these classes, that is what they are defined to do. I don't think these need
to be changed.
For {{DynamicThresholdFilter}} I think it makes sense to go through the
ContextDataInjector rather than querying the ThreadContext.
> Injectable context properties
> -----------------------------
>
> Key: LOG4J2-1010
> URL: https://issues.apache.org/jira/browse/LOG4J2-1010
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.2
> Reporter: Mikael Ståldal
> Assignee: Remko Popma
> Fix For: 2.7
>
> Attachments: properties.patch
>
>
> It would be useful to have a way to inject context properties into a
> {{LogEvent}}, as an alternative to {{ThreadContext}}.
> In an asynchronous environment, using ThreadContext as currently implemented
> is not so useful since JVM threads might not be coupled to the logical flow
> of the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
