[
https://issues.apache.org/jira/browse/ARTEMIS-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578425#comment-16578425
]
ASF subversion and git services commented on ARTEMIS-2027:
----------------------------------------------------------
Commit c1c2d01bc525411d46cef1c7589e4a1e71e42b02 in activemq-artemis's branch
refs/heads/2.6.x from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=c1c2d01 ]
ARTEMIS-2027: handle aborted AMQP deliveries
(cherry picked from commit e1ba608d64883f071442340ed091441187f48a01)
> handle arriving AMQP deliveries being aborted
> ---------------------------------------------
>
> Key: ARTEMIS-2027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.6.2
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 2.7.0, 2.6.3
>
>
> AMQP allows for deliveries to be sent in multiple transfer frames, and as
> part of this also allows for a delivery to be explicitly aborted without
> completing. This scenario can now arise when fronting a receiver such as the
> broker with a Qpid Dispatch router, as it streams larger messages to
> receivers while they are sent to the router. If such messages are in process
> of being sent to the router and the sending connection drops before it
> completes, the router will abort the incomplete delivery to any receivers it
> was streaming the payload to already. The broker should handle such aborted
> deliveries appropriately.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
