logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-256) log4net With MDC is not exactly threadsafe?
Date Sat, 05 Nov 2016 21:55:58 GMT

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

Dominik Psenner commented on LOG4NET-256:
-----------------------------------------

So this is not something that can be fixed within the logging framework, can it?

> log4net With MDC is not exactly threadsafe?
> -------------------------------------------
>
>                 Key: LOG4NET-256
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-256
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.10
>         Environment: Windows Server 2003, Windows XP
>            Reporter: MK Pandey
>             Fix For: 1.2 Maintenance Release
>
>         Attachments: bug detals mail.jpg
>
>
> Hi All, 
> Our situation is that we are using MDC values (ex, transID) to set additional values
which is used across multiple classes to identify the transaction. 
> We have one LogHelper class which creates private static instance of the as below: 
> log4net.ILog fileLogger = LogManager.GetLogger(GetType()); 
> When second thread starts and modifies the values, the subsequent logs from other threads
start using the same values. 
> Any suggestions? 
> When using web.config file for appender defintion, is this not thread safe? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message