logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Grabowski (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LOG4NET-164) using a named mutex for file appenders
Date Sun, 08 Feb 2009 20:20:59 GMT

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

Ron Grabowski updated LOG4NET-164:

    Attachment: MutexProcessLock.patch

Added ProcessLock inner class alongside ExclusiveLock and MinimalLock that uses a Mutex to
allows multiple processes to correctly lock to the same file without having to open and close
the file for each write.

ProcessLock name may need to change...MutexLock, InterProcessLock?

> using a named mutex for file appenders
> --------------------------------------
>                 Key: LOG4NET-164
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-164
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>            Reporter: Frank
>            Assignee: Ron Grabowski
>             Fix For: 1.2.11
>         Attachments: MutexProcessLock.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> About logging to the same file from 2 or more instances of an application.
> As opposed to a minimallock which makes it still possible for 2 application instances
to interfere. Why not use a named mutex so that the logging will wait for the lock to be released
from another instance.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message