[
https://issues.apache.org/jira/browse/LOG4NET-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
MK Pandey updated LOG4NET-256:
------------------------------
Comment: was deleted
(was: Hi All,
So you mean, if we are using web.config file for appender defintion, we can not
have it thread safe?
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? )
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
