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 2017/02/02 11:28:51 UTC

[jira] [Resolved] (LOG4NET-550) Logging recursively from an Appender not supported for NET_4_0 and MONO_4_0

     [ https://issues.apache.org/jira/browse/LOG4NET-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig resolved LOG4NET-550.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.8

merged the PR, many thanks!

> 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
>             Fix For: 2.0.8
>
>
> 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)