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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.7
• Fix Version/s: 2.0.8
• Component/s: Core
• Assignee: Unassigned
• Reporter: Joe
• Created: 01/Feb/17 11:17
• Updated: 02/Feb/17 19:13
• Resolved: 02/Feb/17 11:28

Description

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

Issue Links

• is duplicated by: LOG4NET-551 LockRecursionException when using File Appenders
• links to: GitHub Pull Request #41