[
https://issues.apache.org/jira/browse/LOG4NET-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985588#comment-14985588
]
Dominik Psenner commented on LOG4NET-485:
-----------------------------------------
It's great to hear that it looks great. Obviously it should also work. You
wouldn't have the chance to test it, have you?
I gotta note further that this fix introduces a performance penalty for the
non-inter-process usage of the rolling file appender. This might not be always
the wanted behaviour, but I did not want to introduce yet another configuration
option allowing users to choose if locking should take place or not. Worst case
users configure it wrong and suffer on the collateral damage that will happen.
Anyway, this configuration option could be a great way to improve this appender
further. Let me know what you think about this.
> RollingFileAppender cannot be used by multiple process
> ------------------------------------------------------
>
> Key: LOG4NET-485
> URL: https://issues.apache.org/jira/browse/LOG4NET-485
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.13, 1.2.14, 1.3.0
> Reporter: NN
> Assignee: Dominik Psenner
> Fix For: 1.2.14
>
>
> RollingFileAppender doesn't acquire lock when rolling takes place.
> As a consequence running multiple instances of the same program rewrites the
> same log file instead of making a roll for everyone.
> There is FileAppender.InterProcessLock but it only protects writes and not
> rolls.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
