[
https://issues.apache.org/jira/browse/LOG4NET-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15540773#comment-15540773
]
Richard Collette commented on LOG4NET-418:
------------------------------------------
Seeing reports of this with Log4Net.Async
https://github.com/cjbhaines/Log4Net.Async/issues/30
In the parallel forwarding appender implementation
https://github.com/cjbhaines/Log4Net.Async/blob/master/src/Log4Net.Async/ParallelForwardingAppender.cs
I'm a bit stumped by this because the locking implementation in both
Log4Net.Async and in Logger.cs callAppenders() method have both been around for
quite some time. I'm wondering if this has something to do with libraries
that are being linked to?
> 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.3.4#6332)
