You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Dominik Psenner (JIRA)" <ji...@apache.org> on 2011/08/13 10:20:27 UTC

[jira] [Commented] (LOG4NET-190) [Patch] Need true asynchronous appender

    [ https://issues.apache.org/jira/browse/LOG4NET-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084565#comment-13084565 ] 

Dominik Psenner commented on LOG4NET-190:
-----------------------------------------

Applied the existing patch here: https://bitbucket.org/NachbarsLumpi/log4net-patches

Please discuss.

> [Patch] 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
>             Fix For: 1.2.11
>
>         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.
For more information on JIRA, see: http://www.atlassian.com/software/jira