[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448643#comment-15448643
]
Remko Popma commented on LOG4J2-1010:
-------------------------------------
This is to prepare for the {{LOG4J2-1349-gcfree-threadcontext}} branch.
[ThreadContextDataInjector in that
branch|https://github.com/apache/logging-log4j2/blob/LOG4J2-1349-gcfree-threadcontext/log4j-core/src/main/java/org/apache/logging/log4j/core/impl/ThreadContextDataInjector.java]
handles three ThreadContextMap implementations:
* ContextData-based garbage-free ThreadContextMap
* ContextData-based copy-on-write ThreadContextMap
* Map<String,String> based ThreadContextMap
> 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
