You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Kai Hudalla (JIRA)" <ji...@apache.org> on 2018/05/25 15:51:00 UTC
[jira] [Commented] (DISPATCH-1012) Release undeliverable
deliveries, don't hold them
[ https://issues.apache.org/jira/browse/DISPATCH-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490895#comment-16490895 ]
Kai Hudalla commented on DISPATCH-1012:
---------------------------------------
Any chance this can make it into the 1.1.0 release?
> Release undeliverable deliveries, don't hold them
> -------------------------------------------------
>
> Key: DISPATCH-1012
> URL: https://issues.apache.org/jira/browse/DISPATCH-1012
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Reporter: Ted Ross
> Priority: Major
> Fix For: 1.2.0
>
>
> In 1.1.0, deliveries that are produced into the router network that are undeliverable (i.e. the last consumer for the address has detached) are held in the ingress link's undelivered list. There is no limit to the amount of time that a delivery can remain in this list.
> Rather than hold undeliverable messages in the undelivered list, the router should return them to the sender with RELEASED disposition. Furthermore, once released, credit should not be replenished to the sender until there is a consumer attached to receive the deliveries.
--
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