You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ganesh Murthy (JIRA)" <ji...@apache.org> on 2018/06/28 13:33:00 UTC
[jira] [Resolved] (DISPATCH-1045) Sometimes close connetion after
releasing partial multi-frame messsage
[ https://issues.apache.org/jira/browse/DISPATCH-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ganesh Murthy resolved DISPATCH-1045.
-------------------------------------
Resolution: Fixed
> Sometimes close connetion after releasing partial multi-frame messsage
> ----------------------------------------------------------------------
>
> Key: DISPATCH-1045
> URL: https://issues.apache.org/jira/browse/DISPATCH-1045
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 1.1.0
> Reporter: Alan Conway
> Assignee: Ganesh Murthy
> Priority: Major
> Fix For: 1.2.0
>
>
> Since DISPATCH-1012 the router releases undeliverable deliveries.
> In the case of a multi-frame delivery, it is possible for dispatch to release it before the entire delivery has been received. Presently dispatch settles such deliveries and advances its link. That means that if another transfer for the same delivery arrives, dispatch regards it as a new message with an invalid delivery-id and closes the connection. Since the release is asynchronous, there's no way for the client to avoid this possibility.
> Worth checking the spec but I suspect we should be dropping the extra data rather than closing the connection. Need to investigate how this would work in proton - I think we'd update the delivery without settling it and then wait for the remote to settle before finally throwing it away.
>
--
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