[
https://issues.apache.org/jira/browse/LOG4NET-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888932#comment-13888932
]
Jakub Linhart commented on LOG4NET-407:
---------------------------------------
Many thanks for your AsyncAppender, it will be very useful. Beware using try,
catch, finally inside the lock - it is very costly and most likely will cause
drastic performance drop in massivelly parallel applications like ASP.NET due
to high contention rate. Please, why do you use _recursiveGuard?
> AsyncAppender - better Implementation
> -------------------------------------
>
> Key: LOG4NET-407
> URL: https://issues.apache.org/jira/browse/LOG4NET-407
> Project: Log4net
> Issue Type: Improvement
> Components: Appenders
> Environment: .Net 4.0 and newer
> Reporter: Michael Goldfinger
> Priority: Minor
> Fix For: 1.3.0
>
>
> I checked out the AsyncAppender
> (http://svn.apache.org/viewvc/logging/log4net/trunk/examples/net/2.0/Appenders/SampleAppendersApp/cs/src/Appender/AsyncAppender.cs?view=markup)
> and found some drawbacks.
> * logevents are not logged if the appender close
> * order of logevents got lost
> I created an new implementation that waits for all logevents to be computed
> before close and maintains the order of the events. If the application
> process got killed the logevents are lost too but in any other case the loss
> of logevents could be prevented. The drawback of my implementation is that
> the TLP is requred so .NET 2.0 is not supported.
> I could not find the place to contribute so I created this ticket. I hope
> it's useful.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
