[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447531#comment-15447531 ]
Remko Popma commented on LOG4J2-1010: ------------------------------------- The performance concerns Ralph raised regarding global Filters have been addressed. For further reviews, may I propose that people review the {{LOG4J2-1349-gcfree-threadcontext}} branch instead? It has the same changes as the {{LOG4J2-1010&LOG4J2-1447-injectable-contextdata&better-datastructure}} branch, but in addition moved ContextData and related interfaces to org.apache.logging.log4j.spi package in log4j-api. Without the LOG4J2-1349 changes * context data-based Filters and Lookups need to make an unnecessary copy * injecting context data into the log event needs to make an unnecessary copy > 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