[
https://issues.apache.org/jira/browse/LOG4NET-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279908#comment-13279908
]
Ron Grabowski commented on LOG4NET-339:
---------------------------------------
Can you provide a method name or a better stack trace? The appender eventually
calls down to this:
EventLog.WriteEntry(m_applicationName, eventTxt, entryType, eventID, category);
without any fancy locking. How do you know that WriteEntry isn't the problem?
http://svn.apache.org/viewvc/logging/log4net/trunk/src/Appender/EventLogAppender.cs?view=markup
> log4net.Appender.EventLogAppende cause our application to stuck.
> -----------------------------------------------------------------
>
> Key: LOG4NET-339
> URL: https://issues.apache.org/jira/browse/LOG4NET-339
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: Windows Server 2008 R2 SP1
> Reporter: Yaron Yeshaya
>
> Randomly one of our COM Service (.Net 4.0 Windows service that exposes com
> interface) stop processing com calls. We spoke with Microsoft and sent the
> the application dump file.
> Microsoft claims that from the dump it looks like log4net issue: "we are
> appending the events 04ACEEE0 00f3ba38 log4net.Appender.EventLogAppender and
> we are waiting on it (clr!WaitForMultipleObjectsEx_SO_TOLERANT+0x56 --wait).
> The issue seems to be coming from log4net."
> Did you encountered such an issue?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
