[
https://issues.apache.org/jira/browse/LOG4NET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777552#comment-13777552
]
Stefan Bodewig commented on LOG4NET-232:
----------------------------------------
In that case my VM won't help as it runs XP SP3.
Do you know what kind of exception is raised on older systems?
> Use ReaderWriterLockSlim instead of ReaderWriterLock.
> -----------------------------------------------------
>
> Key: LOG4NET-232
> URL: https://issues.apache.org/jira/browse/LOG4NET-232
> Project: Log4net
> Issue Type: Improvement
> Affects Versions: 1.2.10
> Environment: Any
> Reporter: Aron Weiler
> Assignee: Dominik Psenner
> Priority: Minor
> Fix For: 1.2.12
>
>
> ReaderWriterLock should be replaced with ReaderWriterLockSlim according to
> Microsoft for performance and simplification reasons.
> MSDN:
> http://msdn.microsoft.com/en-us/library/system.threading.readerwriterlock.aspx
> The .NET Framework has two reader-writer locks, ReaderWriterLockSlim and
> ReaderWriterLock. ReaderWriterLockSlim is recommended for all new
> development. ReaderWriterLockSlim is similar to ReaderWriterLock, but it has
> simplified rules for recursion and for upgrading and downgrading lock state.
> ReaderWriterLockSlim avoids many cases of potential deadlock. In addition,
> the performance of ReaderWriterLockSlim is significantly better than
> ReaderWriterLock.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
