You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Martyn Taylor (JIRA)" <ji...@apache.org> on 2017/03/10 12:17:04 UTC

[jira] [Resolved] (ARTEMIS-773) AMQP: Transactional Acquistion and Retirement does not seem to work correctly.

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

Martyn Taylor resolved ARTEMIS-773.
-----------------------------------
    Resolution: Fixed

> AMQP: Transactional Acquistion and Retirement does not seem to work correctly.
> ------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-773
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-773
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 1.4.0
>            Reporter: Timothy Bish
>            Assignee: Martyn Taylor
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> When a message is enlisted in a transaction by having an accepted disposition but is not settled, and the transaction is rolled back by the client, the broker should treat that message as still being acquired by the receiver and not redeliver it again and the receiver should be able to consume, modify, reject or release the delivery on its own afterwards.
> It seems that the broker allows for a client to accept but not settle inside of a TX but if that TX is rolled back it appears that the message will later be redelivered even if they are immediately accepted in a new TX and that TX is committed.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)