[
https://issues.apache.org/jira/browse/PROTON-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561886#comment-16561886
]
ASF subversion and git services commented on PROTON-1902:
---------------------------------------------------------
Commit b5cd0a4601d58b3fc5440cf3f586922fcf3993ea in qpid-proton-j's branch
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=b5cd0a4 ]
PROTON-1902: fix/allow handling of aborted deliveries
Ensure 'aborted' flag overrules the 'more' and 'settled' flags as appropriate,
account for delivery properly, and allow determining it was aborted.
> arriving aborted transfers are mishandled and can't be observed
> ---------------------------------------------------------------
>
> Key: PROTON-1902
> URL: https://issues.apache.org/jira/browse/PROTON-1902
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: proton-j-0.27.2, proton-j-0.28.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: proton-j-0.29.0
>
>
> When an arriving delivery is aborted by its final transfer frame, the
> transport session mishandles it. The 'aborted' flag is not considered
> properly and fails to override the flags for 'more' and 'settled' (aborted
> deliveries are implicitly settled), the transfer frames payload if any is not
> discarded as required, and the delivery count and credit aren't updated, so
> any future flow frames sent will fail to account for it properly. No attempt
> is made to track that the abort happened, so there is also no way for the
> using application code to detect that the delivery was aborted and will
> remain 'partial' indefinitely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
