logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method
Date Mon, 10 Aug 2015 05:47:45 GMT

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

Ralph Goers edited comment on LOG4J2-1010 at 8/10/15 5:47 AM:
--------------------------------------------------------------

1. CustomMapMessage is used to allow you to specify a message along with the properties map.
If you just use MapMessage then the %m pattern will display the entire property map as the
message.
2. The properties map passed to CustomMapMessage does not have to be a ConcurrentHashMap.
It is that way because I copied the first example to the second and then modified it. 
3. Do you have suggestions on how the LoggerConfig would know what keys to add without specifying
them in the configuration? 

Note that instead of specifying them on the logger you could use the lookup in the pattern
layout - but you said you didn't want to do that.

Can you provide more details on what your custom lookup was trying to do and why you could
not get it to work?


was (Author: ralph.goers@dslextreme.com):
1. CustomMapMessage is used to allow you to specify a message along with the properties map.
If you just use MapMessage then the %m pattern will display the entire property map as the
message.
2. The properties map passed to CustomMapMessage does not have to be a ConcurrentHashMap.
It is that way because I copied the first example to the second and then modified it. 
3. Do you have suggestions on how the LoggerConfig would know what keys to add without specifying
them in the configuration? 

Note that instead of specifying them on the logger you could use the lookup in the pattern
layout - but you said you didn't want to do that.

> 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