logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikael Ståldal (JIRA) <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method
Date Thu, 06 Aug 2015 11:37:05 GMT

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

Mikael Ståldal commented on LOG4J2-1010:

Thanks Ralph, this looks really interesting. I would like something like this to be added
to log4j-core. Perhaps the {{CustomMapMessage}} should allow nesting another {{Message}} as
well as a plain string?

Question: is it necessary for the properties map to be thread-safe when using {{CustomMapMessage}}?
I.e. does it really have to be {{ConcurrentHashMap}}, or would a standard {{HashMap}} be sufficient?

However, I find it annoying that I have to declare all properties ({{key1}} and {{key2}} in
the sample) in the config file.

> Possibility to set ThreadContext values in calls to Logger method
> -----------------------------------------------------------------
>                 Key: LOG4J2-1010
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1010
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 2.2
>            Reporter: Mikael Ståldal
> It would be useful to have some logging methods in the Logger interface to set ThreadContext
values for a single log message only.
> In an asynchronous environment, using ThreadContext as currently defined 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