You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2021/03/24 10:50:00 UTC

[jira] [Updated] (AMQ-8201) ACK compaction with local transactions

     [ https://issues.apache.org/jira/browse/AMQ-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated AMQ-8201:
--------------------------------------
    Fix Version/s: 5.16.2
                   5.15.15
                   5.17.0

> ACK compaction with local transactions
> --------------------------------------
>
>                 Key: AMQ-8201
>                 URL: https://issues.apache.org/jira/browse/AMQ-8201
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.16.1, 5.15.14
>            Reporter: Jonathan Gallimore
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.17.0, 5.15.15, 5.16.2
>
>
> 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
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)