Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Date: Fri, 22 Nov 2013 17:58:40 +0000 (UTC)
From: "Stefan Bodewig (JIRA)" <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: <JIRA.12680788.1385143112734.15724.1385143120133@arcas>
In-Reply-To: <JIRA.12680788.1385143112734@arcas>
References: <JIRA.12680788.1385143112734@arcas>
Subject: [jira] [Created] (LOG4NET-408) Correction on InterProcessLock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Stefan Bodewig created LOG4NET-408:
--------------------------------------

             Summary: 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)