[
https://issues.apache.org/jira/browse/LOG4NET-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860806#action_12860806
]
MK Pandey commented on LOG4NET-199:
-----------------------------------
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 not exactly threadsafe?
> -------------------------------
>
> Key: LOG4NET-199
> URL: https://issues.apache.org/jira/browse/LOG4NET-199
> Project: Log4net
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.10
> Environment: Windows Server 2003
> Reporter: Kenneth Shih
> Attachments: ThreadingTest.cs
>
>
>
> Problem: We call log4net from our BizTalk 2006 orchestrations. We noticed we
> were missing logging data.
>
> Doing a simple Nunit single threaded test, we would get all logged data.
> (repeatable)
> In a Nunit multithreaded test, we would notice missed logged data.
> (repeatable)
> Also, we also noticed when BizTalk Host, when we lowered the amount of
> active threads down to 2 (the lowest we could go)
>
> So, We enabled debug tracing in log4net. We also added various system.diag
> eventlogwrites around different parts of our code, from where log4net was
> called, and also inside our appenders.
>
> We noticed was saw an error in the debug tracing (using debugviewer)
> log4net:ERROR [EventLogAppender] Attempted to append to closed appender named
> [EventLogAppender].
>
> Also, by counting the number of eventlog entries we had from the various
> points, log4net itself was not calling the appenders each time it was called
> to log a message.
>
> We seen this issue of log4net not calling the appenders, with a variety of
> different appenders, like the out of the box file and eventlog appenders and
> also our own msmq appender.
>
> So log4net doesn't appear to be thread safe? Any suggestions?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
