logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Sargisson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-269) Berkeley (persistent) agent for FlumeAppender does not work if batch size is 1 (the default)
Date Tue, 28 May 2013 17:53:20 GMT
Edward Sargisson created LOG4J2-269:
---------------------------------------

             Summary: Berkeley (persistent) agent for FlumeAppender does not work if batch
size is 1 (the default)
                 Key: LOG4J2-269
                 URL: https://issues.apache.org/jira/browse/LOG4J2-269
             Project: Log4j 2
          Issue Type: Bug
            Reporter: Edward Sargisson


Repro steps:
Use persistent agent from the FlumeAppender while the succeeding Flume agent is down.

Expected result:
Logs should queue.

Actual result:
2013-05-28 17:02:12,921 ERROR Unable to delete event java.lang.UnsupportedOperationException:
A transacti
on was not supplied when opening this cursor: delete
        at com.sleepycat.je.Cursor.checkUpdatesAllowed(Cursor.java:4007)
        at com.sleepycat.je.Cursor.delete(Cursor.java:689)
        at org.apache.logging.log4j.flume.appender.FlumePersistentManager$WriterThread.run(FlumePersisten
tManager.java:448)

Workaround:
Set the batchSize to a number > 1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


Mime
View raw message