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, 03 Aug 2015 01:43:04 GMT

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

Ralph Goers edited comment on LOG4J2-1010 at 8/3/15 1:42 AM:
-------------------------------------------------------------

I have created a loggerProperties sample project in the log4j-samples module. There are two
variations. The first uses a custom lookup that registers a Map by logger name. The second
uses a custom MapMessage and a custom lookup to retrieve the properties from the message.
With a little massaging these could probably be added to core as standard components.

I also had to make a slight change to loggerConfig as it was not passing the logEvent to the
Lookup.


was (Author: ralph.goers@dslextreme.com):
I have created a loggerProperties sample project in the log4j-samples module. There are two
variations. The first uses a custom lookup that registers a Map by logger name. The second
uses a custom MapMessage and a custom lookup to retrieve the properties from the message.
With a little massaging these could probably be added to core as standard components.

> 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