[LOG4J2-269] Berkeley (persistent) agent for FlumeAppender does not work if batch size is 1 (the default)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-beta7
• Assignee: Unassigned
• Reporter: Edward Sargisson
• Created: 28/May/13 17:51
• Updated: 30/May/13 18:44
• Resolved: 29/May/13 23:59

Description

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.