logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Grabowski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-339) log4net.Appender.EventLogAppende cause our application to stuck.
Date Sun, 27 May 2012 20:17:22 GMT

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

Ron Grabowski commented on LOG4NET-339:

I've never really dug deep into memory dump so that wasn't very helpful to me. If you have
a lot of control over your environment and you know that all the event log busy work stuff
has been setup correctly you could just write your own appender to forward log messages to

public class ApplicationNameEventLogAppender : AppenderSkeleton
    protected override void Append(LoggingEvent loggingEvent)
        EventLog.WriteEntry("ApplicationName", RenderLoggingEvent(loggingEvent), EventLogEntryType.Information);

That would eliminate log4net's EventLogAppender as the problem.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message