You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2018/06/27 22:16:00 UTC
[jira] [Resolved] (DISPATCH-1020) Detach expiring links with
closed=true when peer connectivity lost
[ https://issues.apache.org/jira/browse/DISPATCH-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved DISPATCH-1020.
----------------------------------
Resolution: Fixed
> Detach expiring links with closed=true when peer connectivity lost
> ------------------------------------------------------------------
>
> Key: DISPATCH-1020
> URL: https://issues.apache.org/jira/browse/DISPATCH-1020
> Project: Qpid Dispatch
> Issue Type: Improvement
> Reporter: Keith Wall
> Assignee: Ganesh Murthy
> Priority: Major
> Fix For: 1.2.0
>
>
> Currently, Dispatch responds to the loss of an underlying connection to a peer by detaching the links established over that connection in the following way.
> {noformat}
> @detach(22) [handle=0, closed=false, error=@error(29) [condition=:"qd:routed-link-lost", description="Connectivity to the peer container was lost”]]
> {noformat}
> As is makes no sense for link defined to expire to attached again, it would be an improvement to the dispatch's behaviour if those links were detached with {{closed=true}}. This would aid the timely clean-up of resources elsewhere in the AMQP network.
--
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