logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1010) Injectable context properties
Date Sun, 28 Aug 2016 15:41:21 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443634#comment-15443634

Remko Popma commented on LOG4J2-1010:

[~ralph.goers@dslextreme.com] {{ContextDataInjector}} now has a new method that gives access
to the raw underlying {{ContextData}} without any copying. I updated the affected filters
and lookups to use this method.

Note that in the {{LOG4J2-1010&LOG4J2-1447-injectable-contextdata&better-datastructure}}
branch the {{ThreadContextDataInjector}} implementation still copies the data. 

To rectify this, in the LOG4J2-1349 branch {{DefaultThreadContextMap}} now implements the
ContextData interface. This results in a much more efficiently performing implementation.

> 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message