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 13:19:04 GMT

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

Mikael Ståldal commented on LOG4J2-1010:
----------------------------------------

After some testing, I realized that {{MapMessageLookup}} is not needed, and not used. {{MapLookup}}
in log4j-core is used for a {{MapMessage}}, and the lookup prefix in config file can be anything
(I tried with "foo" and it worked equally well as "mapMessage").



> 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
(v6.3.4#6332)

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


Mime
View raw message