Hi,
I added a Jira issue (https://issues.apache.org/jira/browse/LOG4NET-443)
for it to keep track of the investigations.
Best regards,
Calin Pavel
On 10/18/2014 8:41 AM, Stefan Bodewig wrote:
On 2014-10-17, Calin Pavel wrote:
Did you encountered this before or did anybody else reported similar
problems?
This is the first time I've heard of the problem and I can't find a
report about that in JIRA. We've only introduced support for
ReaderWriterLockSlim in 1.2.12, so earlier versions should not be
affected (but likely won't run on .NET 4.5).
In relation with this, I found a possible explanation of application
hanging here:
http://chabster.blogspot.ro/2013/07/a-story-of-orphaned-readerwriterlockslim.html
Could it be that the acquire of read lock in Logger.CallAppenderers
method to generate our problems?
In order to trigger the problem mentioned in the article you cite
threads holding writer locks must have been aborted, this might be the
case as you write
- that my threads have a timeout, and if they do not finish the job in
the given interval they are aborted.
I haven't followed the solution outlined in your link but it sounds as
if we could give it a try. Could you please open a JIRA issue at
https://issues.apache.org/jira/browse/LOG4NET so we have a place to
track the problem and point at if anybody else encounters it?
Thanks for your research
Stefan
