You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2016/09/29 14:00:31 UTC

[jira] [Updated] (AMQ-6444) AMQP: Messages in a Transaction which aren't settled should be remain acquired for the receiver after rollback

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

Robbie Gemmell updated AMQ-6444:
--------------------------------
    Description: 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.  (was: When a message is enlisted in a transaction by having an accepted disposition but is not settled 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 consumer, modify, reject or release the delivery on its own afterwards.)
        Summary: AMQP: Messages in a Transaction which aren't settled should be remain acquired for the receiver after rollback  (was: AMQP: Messages in a Transaction which aren't settled should be remain acquired on the receiver)

> AMQP: Messages in a Transaction which aren't settled should be remain acquired for the receiver after rollback
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6444
>                 URL: https://issues.apache.org/jira/browse/AMQ-6444
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 5.14.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.15.0, 5.14.2
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)