logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-489) Should JPADatabaseManager being using so many transactions?
Date Tue, 07 Jan 2014 03:33:50 GMT
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

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

View raw message