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

ASF GitHub Bot commented on ARTEMIS-2027:
-----------------------------------------

GitHub user gemmellr opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2245

    ARTEMIS-2027: handle aborted AMQP deliveries

    Fixes handling of aborted deliveries to ensure the receiver processes the 
delivery (and any subsequent ones) appropriately. Unit tested only since 
Proton-J cant send aborted deliveries, though I have also verified it with 
modified client (slowed down) sending from client-> Dispatch -> Artemis and 
back and killing the client connection mid-send.
    
    I'd like this backported to 2.6.x also.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gemmellr/activemq-artemis delivery-aborted

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2245.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2245
    
----
commit e1ba608d64883f071442340ed091441187f48a01
Author: Robbie Gemmell <robbie@...>
Date:   2018-08-13T13:01:01Z

    ARTEMIS-2027: handle aborted AMQP deliveries

----


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

Reply via email to