Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Tue, 7 Jan 2014 03:33:50 +0000 (UTC)
From: "Matt Sicker (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12687584.1389065576688.52405.1389065630769@arcas>
In-Reply-To: <JIRA.12687584.1389065576688@arcas>
References: <JIRA.12687584.1389065576688@arcas>
Subject: [jira] [Created] (LOG4J2-489) Should JPADatabaseManager being using
 so many transactions?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Matt Sicker created LOG4J2-489:
----------------------------------

             Summary: Should JPADatabaseManager being using so many transactions?
                 Key: LOG4J2-489
                 URL: https://issues.apache.org/jira/browse/LOG4J2-489
             Project: Log4j 2
          Issue Type: Improvement
          Components: Appenders
    Affects Versions: 2.0
         Environment: JPA appender
            Reporter: Matt Sicker
            Priority: Minor


Even when the appender is buffered, every log event is still committed each time. In JDBCAppender, when it's buffered, log events aren't inserted into the database until the buffer is full.

I tried to address this while I was working on another patch, but there's no good way to generate an EntityTransaction without the EntityManager, and that's recreated each time writeInternal() is called.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org