logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Mrkonjic (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-418) Recursive read lock acquisitions not allowed in this mode.
Date Wed, 29 Jun 2016 10:27:37 GMT

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

Robert Mrkonjic commented on LOG4NET-418:


I have the same issue which ends critical. We are using log4net in a WCF service hosted as
a Windows Service and after update to 1.2.15 we experience that service crashes unexpectedly
and log says nothing about cause of it. Extensive investigation has shown that log4net throws
many LockRecursionException which fill up the stack and end in a stackoverflowexception which
crashes the service. Unfortunately, cannot pinpoint the place in code where it happens.

According to the latest comments of other users, this ticker should not be marked as Resolved
as the bug is still active. Please, provide us with some hint how to solve this issue or at
least some hint what the cause of this issue could be. Thanks in advance!

> Recursive read lock acquisitions not allowed in this mode.
> ----------------------------------------------------------
>                 Key: LOG4NET-418
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-418
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>            Reporter: Fabio Marini
> I'm getting the unhandled exception above when calling log.Logger.Repository.GetAppenders();
- understand unhandled exceptions should not occur and should be treated as bugs?

This message was sent by Atlassian JIRA

View raw message