You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/10/06 18:20:20 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15552723#comment-15552723 ] 

ASF subversion and git services commented on AMQ-6444:
------------------------------------------------------

Commit baef8f8ec20ed3057895f6ec1e02ca6ea75a33a1 in activemq's branch refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=baef8f8 ]

https://issues.apache.org/jira/browse/AMQ-6444

Remove some unneeded instance of checks and used cached values where
possible.

> 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)