logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method
Date Thu, 23 Jun 2016 11:18:16 GMT

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

Greg Thomas commented on LOG4J2-1010:

> void logMessage(String fqcn, Level level, Marker marker, Message message, Throwable t,
Map<String, String> contextMap);

My issue with this solution is the client code must explicitly pass in the context. 

For my particular use case, we call out to the Apache HttpClient library. This logs using
Apache Commons Logging, which I can re-route through to log4j2 using the log4j-jcl adapter.
This means I can set the ThreadContext up front, call the libraries I wish, and those libraries
will happily log with the right ThreadContext even if they know nothing about it. And, in
the case of Apache HttpClient, even if their underlying logging framework has no concept of
a ThreadContext/MDC/NDC.

I appreciate that this would solve the problem as phrased by this issue ("set ThreadContext
values in calls to Logger method"), but I think the issue as currently phrased is highlighting
a single solution rather than identifying the underlying problem.

> 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
>         Attachments: properties.patch
> 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