[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma reopened LOG4J2-1010: --------------------------------- Reopening since Ralph found that the FilterPerformanceComparison performance test showed a large performance regression. The cause of the regression is that a new context data instance is created for each call to getMutableContextData() if the thread context is empty. The solution is to return a cached empty instance. Filters don't need a mutable instance. > 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