[
https://issues.apache.org/jira/browse/DISPATCH-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245617#comment-16245617
]
ASF subversion and git services commented on DISPATCH-870:
----------------------------------------------------------
Commit 21fcf9808da77fc8ea1858c2280a2ad05947e9c8 in qpid-dispatch's branch
refs/heads/1.0.x from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=21fcf98 ]
DISPATCH-870 - Fix ref-counting on server connections so deleted connectors
result in closed connections.
> connection improperly reopened from closed connector
> ----------------------------------------------------
>
> Key: DISPATCH-870
> URL: https://issues.apache.org/jira/browse/DISPATCH-870
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Affects Versions: 1.0.0
> Reporter: michael goulish
> Assignee: Ted Ross
> Priority: Blocker
> Fix For: 1.0.0
>
>
> I have a 3-mesh router network, ABC, and I am sending messages from B to C.
> The route being used is B,A,C -- because I have configured it to be cheaper
> than B,C .
> I use the management interface to kill the connector from C to A. For the
> next two seconds my messages are released. I use another management call to
> confirm that the connector has really been removed. ( I also see it happening
> in the C code, at fn qd_connection_manager_delete_connector() . )
> What We Expect: the network should re-route to start sending these messages
> on the route B,C -- because that is now the only route available.
> What We Observe: after 2 seconds, the function try_open_lh() is called. It
> reopens the connection from C to A even though the connector has been removed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
