[
https://issues.apache.org/jira/browse/LOG4NET-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287130#comment-13287130
]
Tom Tang commented on LOG4NET-344:
----------------------------------
Hi, Ron:
Thanks for this recommendation.
This one is cool for large amount of logging insertion.
Although it uses async way on doing log, but the bulk insertion strategy
may not good to be everywhere.
Bulk insertion do table lock for efficiency concern, that one I don't like.
I prefer to do normal insertion within small piece data(buffersize is
small) to represent system healthy info ASAP. And thousands of threads or
processes could do concurrent accessing by log4net.
As I know, normal data insertion by simple SQL statement wouldn't lock
table, but bulk-insertion does.
But that one is still cool, I would like to use for other purpose in future.
Thanks for the recommendation again.
Cheers
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
