[DISPATCH-870] connection improperly reopened from closed connector

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0
• Component/s: Routing Engine
• Assignee: Ted Ross
• Reporter: Michael Goulish
• Created: 03/Nov/17 19:04
• Updated: 28/Nov/17 14:43
• Resolved: 09/Nov/17 13:19

Description

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.

Issue Links

• is related to: DISPATCH-887 Dispatch reestablishes connection inspite of deleting the connector
• links to: GitHub Pull Request #214