logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-550) Logging recursively from an Appender not supported for NET_4_0 and MONO_4_0
Date Thu, 02 Feb 2017 11:26:51 GMT

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

ASF GitHub Bot commented on LOG4NET-550:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/log4net/pull/41


> Logging recursively from an Appender not supported for NET_4_0 and MONO_4_0
> ---------------------------------------------------------------------------
>
>                 Key: LOG4NET-550
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-550
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.7
>            Reporter: Joe
>            Priority: Minor
>
> When NET_4_0 or MONO_4_0 is defined, log4net uses a ReaderWriterLockSlim with LockRecursionPolicy.NoRecursion.
 As a result, any attempt to log recursively from within an Appender fail: a System.Threading.LockRecursionException
is thrown and swallowed by the log4net Core.
> Other versions use a ReaderWriterLock and allow recursion.
> The following branch adds a unit test that shows this inconsistent behaviour.  The test
fails for NET_4_0 or MONO_4_0 and passes for other versions:
> https://github.com/JJoe2/log4net/tree/RecursiveLogging



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message