activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-773) AMQP: Transactional Acquistion and Retirement does not seem to work correctly.
Date Fri, 07 Oct 2016 15:09:21 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555331#comment-15555331
] 

ASF subversion and git services commented on ARTEMIS-773:
---------------------------------------------------------

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

ARTEMIS-773 Tests that show issue with TX acquisition and retirement.

Two new tests that acquire messages inside a TX and manage their
settlement and retirement in differing ways, one test works the other
'testReceiversCommitAndRollbackWithMultipleSessionsInSingleTXNoSettlement' 
fails due to messages that were committed being redelivered to the
client unexpectedly.  

> 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
>
> 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.4#6332)

Mime
View raw message