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/02/23 18:40:01 UTC
[jira] [Resolved] (DISPATCH-927) detach not echoed back on
multi-hop link route
[ https://issues.apache.org/jira/browse/DISPATCH-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved DISPATCH-927.
---------------------------------
Resolution: Fixed
> detach not echoed back on multi-hop link route
> ----------------------------------------------
>
> Key: DISPATCH-927
> URL: https://issues.apache.org/jira/browse/DISPATCH-927
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 1.0.0
> Reporter: Gordon Sim
> Assignee: Ganesh Murthy
> Priority: Major
> Fix For: 1.1.0
>
> Attachments: DISPATCH-927.patch, broker.xml, simple-topic-a.conf, simple-topic-b.conf, simple_recv_modified.py
>
>
> In a two router network, router-a and router-b, a link route is defined in both directions on both routers. There is also an associated connector to a broker on router-b. The address is configured to be a topic on the broker.
> If two receivers attach on this address to router-a, and then detach at the same time having received the defined number of messages, frequently (but not always), one of the receivers will not get a detach echoed back to it.
> On inspection of protocol traces, it appears that router-b, though it gets the detach echoed back from the broker, does not forward this back to the client (via router-a).
--
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