You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2014/02/05 21:26:10 UTC

[jira] [Commented] (LOG4NET-418) Recursive read lock acquisitions not allowed in this mode.

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

Stefan Bodewig commented on LOG4NET-418:
----------------------------------------

I agree this shouldn't happen but it seems to be an unforseen case.  Any chance you can provide a bit more of a stacktrace and background on how this happens?

We may also need to know about your platform as on first glance I don't see any explicit locking going on and it may be related to the standard library implementation you use.

> 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
(v6.1.5#6160)