Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-8201

ACK compaction with local transactions

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.16.1, 5.15.14
    • Fix Version/s: 5.17.0, 5.15.15, 5.16.2
    • Component/s: Broker
    • Labels:
      None

      Description

      I have a consumer running with transacted sessions, and looking in KahaDB, I can see a KAHA_REMOVE_MESSAGE_COMMAND, with the local transaction ID added to the journal, and then a KAHA_COMMIT_COMMAND after it. Some time later, I see the exact same KAHA_REMOVE_MESSAGE_COMMAND appended to the journal again, with the exact same transaction information, but no corresponding KAHA_COMMIT_COMMAND. This appears to follow a KAHA_REWRITTEN_DATA_FILE_COMMAND.
       
      It looks like the ack compaction method is forwarding the acknowledgement, but not the commit - it appears that the commit is only forwarded in the case of an XA transaction.
       
      A test and patch is available in the PR here: https://github.com/apache/activemq/pull/636
       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jbonofre Jean-Baptiste Onofré
                Reporter:
                jgallimore Jonathan Gallimore
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: