Log4j 2
  1. Log4j 2
  2. LOG4J2-269

Berkeley (persistent) agent for FlumeAppender does not work if batch size is 1 (the default)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-beta7
    • Component/s: None
    • Labels:
      None

      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.

        Activity

        Hide
        Ralph Goers added a comment -

        Resolved in revision 1487685. Please verify and close.

        Show
        Ralph Goers added a comment - Resolved in revision 1487685. Please verify and close.
        Hide
        Edward Sargisson added a comment -

        I have verified this in my local testing and am now closing it.

        Show
        Edward Sargisson added a comment - I have verified this in my local testing and am now closing it.

          People

          • Assignee:
            Unassigned
            Reporter:
            Edward Sargisson
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development