Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Date: Thu, 31 May 2012 04:25:22 +0000 (UTC)
From: "Tom Tang (JIRA)" <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: <950271312.20226.1338438323018.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (LOG4NET-344) Make AdoNetAppender not to stuck
 application process
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tom Tang created LOG4NET-344:
--------------------------------

             Summary: 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
             Fix For: 3.5


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