[
https://issues.apache.org/jira/browse/AMQ-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530616#comment-15530616
]
ASF subversion and git services commented on AMQ-6444:
------------------------------------------------------
Commit aa32a0f7925c4981aca9a4369b5e95f3336cde94 in activemq's branch
refs/heads/activemq-5.14.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=aa32a0f ]
https://issues.apache.org/jira/browse/AMQ-6444
Ensure that unsettled TX messages remain acquired and not redelivered to
the receiver. Add several tests that demonstrate that a received
message can be released, rejected, accepted or modified after a TX
rollback if it was not settled.
(cherry picked from commit 0dd806f43f3bee9372ee9b9481089d417c265dfe)
> AMQP: Messages in a Transaction which aren't settled should be remain
> acquired on the receiver
> ----------------------------------------------------------------------------------------------
>
> 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 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
