[
https://issues.apache.org/jira/browse/LOG4NET-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632588#comment-16632588
]
Dominik Psenner edited comment on LOG4NET-487 at 9/28/18 10:10 PM:
-------------------------------------------------------------------
The branch now builds. See [this
page|https://builds.apache.org/job/logging-log4net/job/feature%252Frfa-configurable-rolling-mutex/].
The test implementations are still missing. [~andrei_s], would you volunteer
filling those added test stubs with code and file them as a pull request? A
pull request is also built by our CI automatically. This means that CI also
runs your tests and you get feedback.
was (Author: nachbarslumpi):
The branch now builds. The test implementations are still missing. Would you
volunteer filling those added test stubs with code and file them as a pull
request?
> Control mutex type
> ------------------
>
> Key: LOG4NET-487
> URL: https://issues.apache.org/jira/browse/LOG4NET-487
> Project: Log4net
> Issue Type: Improvement
> Components: Appenders
> Affects Versions: 1.2.14, 1.3.0
> Reporter: NN
> Assignee: Dominik Psenner
> Priority: Major
>
> The only missing feature is an option for choosing Local (per session) or
> Global (per machine) mutex.
> The current code just uses the filename for mutex which good but it always
> makes a local one, so if you have two sessions you cannot synchronize them.
> Default is Local for backward compatibility.
> See Note in:
> https://msdn.microsoft.com/en-us/library/system.threading.mutex%28v=vs.110%29.aspx
>
> I think it can be an option like
> <RollingMutexType value="Global" />
> or something like that.
> It also applies to FileAppender mutex .
> <LockingModel InterProcessLock>
> <LockingMutexType value="Global" />
> </..>
> See issue #485 for reference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
