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] [Closed] (LOG4NET-339) log4net.Appender.EventLogAppende cause our application to stuck.
Date Wed, 07 Aug 2013 12:52:52 GMT

     [ https://issues.apache.org/jira/browse/LOG4NET-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dominik Psenner closed LOG4NET-339.

    Resolution: Cannot Reproduce

Closing the issue due to no activity. Feel free to reopen the issue if you can give us more
information on how to reproduce it.
> 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
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message