logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4NET-408) Correction on InterProcessLock
Date Sat, 23 Nov 2013 06:32:35 GMT

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

Stefan Bodewig resolved LOG4NET-408.
------------------------------------

    Resolution: Fixed

svn revision 1544744.

> Correction on InterProcessLock
> ------------------------------
>
>                 Key: LOG4NET-408
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-408
>             Project: Log4net
>          Issue Type: Bug
>            Reporter: Stefan Bodewig
>             Fix For: 1.3.0
>
>
> This is github pull request 6: https://github.com/apache/log4net/pull/6
> {quote}
> This correction enables opening a new file without causing all the AcquireLock blocking
with AbandonedMutexException caused by incorrect state on ReleaseLock, namely m_mutexClosed.
> The bug was found using InterProcessLockwith RollingFileAppender with date pattern on
file name, at midnight the new file is opened and all logging becomes blocked at InterProcessLock.AcquireLock
on m_mutex.WaitOne.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message