[
https://issues.apache.org/jira/browse/PROTON-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576742#comment-16576742
]
Andrew Stitcher edited comment on PROTON-1914 at 4/23/20, 12:55 AM:
--------------------------------------------------------------------
There is a reproducer for this bug at:
[https://github.com/apache/qpid-proton/blob/master/c/tests/connection_driver_test.cpp#L533|https://github.com/apache/qpid-proton/blob/master/c/tests/connection_driver_test.c#L533]
[Edit to fix github link]
was (Author: aconway):
There is a reproducer for this bug at:
[https://github.com/apache/qpid-proton/blob/master/c/tests/connection_driver_test.c#L533]
[Edit to fix github link]
> [c] receiver cannot settle an incomplete incoming message
> ---------------------------------------------------------
>
> Key: PROTON-1914
> URL: https://issues.apache.org/jira/browse/PROTON-1914
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: proton-c-0.24.0
> Reporter: Alan Conway
> Priority: Major
>
> AMQP allows a receiver to settle an incoming message before it has all been
> received, e.g. to reject a large message without receiving it all. However
> the receiver must still be prepared to receive frames of the message that
> might have been in flight, until it gets the remote settle.
> Proton does not support this. Settling an incomplete incoming message
> advances the receiver's delivery-id. Subsequent frames cause and error like:
> "amqp:session:invalid-field:sequencing error, expected delivery-id 1, got 0"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
