[jira] Updated: (LOG4NET-190) Need true asynchronous appender

["Kenneth Xu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4NET-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Xu updated LOG4NET-190:
-------------------------------

    Attachment: AsyncAppenderPatch.patch

This patch is based on trunk r727418. It include following feature and enhancement.

1. Added a true asynchronous appender. It is an forwarding appender that manages it's own event queue and the worker thread. DoAppend returns as soon as the event is added to the queue, the working thread then wake up and forward events to the attached appenders. Event forwarding can be further configured to use batch.
2. Enhanced the BufferingAppenderSkeleton to improve the performance of bulk logging when buffering is disable and not in lossy mode. This is important when extended appenders, e.g. AdoNetAppender, are used to attached to AsycnAppender, which does the buffering already.

> Need true asynchronous appender
> -------------------------------
>
>                 Key: LOG4NET-190
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-190
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.11
>         Environment: DotNet
>            Reporter: Kenneth Xu
>         Attachments: AsyncAppenderPatch.patch
>
>
> The AsycAppender in the example uses .Net ThreadPool, a busy logging system can quickly fill up the queue of the work item. As the ThreadPool is also used by the framework itself, using it for async logging is inappropriate. Thus, a true asynchronous appender with its dedicated queue and thread has been asked by the community many times.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.