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 2016/08/13 13:35:20 UTC
[jira] [Commented] (LOG4NET-466) "LockRecursionException: A read
lock may not be acquired with the write lock held in this mode." exception
[ https://issues.apache.org/jira/browse/LOG4NET-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419923#comment-15419923 ]
Stefan Bodewig commented on LOG4NET-466:
----------------------------------------
does it still happen with 1.2.14 or 1.2.15? LOG4NET-443 has been fixed in 1.2.14.
> "LockRecursionException: A read lock may not be acquired with the write lock held in this mode." exception
> ----------------------------------------------------------------------------------------------------------
>
> Key: LOG4NET-466
> URL: https://issues.apache.org/jira/browse/LOG4NET-466
> Project: Log4net
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.13
> Environment: Windows 7 x64 / .NET 4.5.2
> Reporter: Andrei Faber
>
> I'm getting this exception when trying to call ILog.Error() method (the logger used is RollingFileAppender):
> log4net:ERROR Exception while logging
> System.Threading.LockRecursionException: A read lock may not be acquired with the write lock held in this mode.
> at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout)
> at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout)
> at System.Threading.ReaderWriterLockSlim.EnterReadLock()
> at log4net.Util.ReaderWriterLock.AcquireReaderLock()
> at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent)
> at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception)
> at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception)
> Any ideas why it might be happening?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)