logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ghanshyam (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4NET-344) Make AdoNetAppender not to stuck application process
Date Fri, 23 Jan 2015 01:07:35 GMT

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

Ghanshyam  edited comment on LOG4NET-344 at 1/23/15 1:07 AM:
-------------------------------------------------------------

Stefan, I know this is an old thread. But I could not find information if the above contribution
made it to the main branch. Is this merged into main branch? I am using latest log4net but
am still seeing performance problems with the ado net appender which I don't see with rolling
file appender. Hence the question.


was (Author: ghanashyaml):
Stefan, I know this is an old thread. But I could not find information if the above contribution
made it to the main branch. Is this merged into main branch? I am using latest log4net but
am still seeing performance problems with the ado net appended which I don't see with rolling
file appended. Hence the question.

> Make AdoNetAppender not to stuck application process
> ----------------------------------------------------
>
>                 Key: LOG4NET-344
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-344
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: Windows series
>            Reporter: Tom Tang
>              Labels: patch
>             Fix For: 3.5
>
>         Attachments: AdoNetAppender.cs, AsyncForwardingAppender.cs
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The original AdoNetAppender could stuck application during log insertion.
> Because it use the sync method call to do database insert, once the DB is unavailable
or table was locked.
> I change the implementation that has an inner queue inside to store the messages, and
the other independent thread will be going to cunsuming the queue messages and do DB insertion.
> This implementation will not have any impact on application performance and much stable.
> Trade off: Once the queue max buffer was full, the later coming log message would be
ignored and gone forever. But log4net is not designed for guarantee delivery in purpose, right?
So it's not big deal at all. :)  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message