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 2015/08/23 16:45:45 UTC

[jira] [Updated] (LOG4NET-408) Correction on InterProcessLock

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

Stefan Bodewig updated LOG4NET-408:
-----------------------------------
    Fix Version/s: 1.2.14

> 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.2.14, 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.3.4#6332)