You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/08/10 19:05:00 UTC
[jira] [Commented] (PROTON-1914) [c] receiver cannot settle an
incomplete incoming message
[ https://issues.apache.org/jira/browse/PROTON-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576738#comment-16576738 ]
ASF subversion and git services commented on PROTON-1914:
---------------------------------------------------------
Commit 1d64ea54d7609471d322585d907e0b330c3fc5cf in qpid-proton's branch refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1d64ea5 ]
PROTON-1914: [c] reproducer for settling an incomplete incoming
> [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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org