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

Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/04/04 22:29:03 UTC

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

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

Ralph Goers updated LOG4NET-190:
--------------------------------

LOG4NET is now dormant.  

> [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
>            Priority: Major
>             Fix For: 1.2/2.0 Maintenance Release
>
>         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 was sent by Atlassian Jira
(v8.3.4#803005)