[DISPATCH-32] Undeliverable messages should get released.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.2
• Fix Version/s: 0.6.0
• Component/s: Router Node

Environment

cold, snowy.

• Assignee: Ted Ross
• Reporter: Michael Goulish
• Created: 28/Feb/14 20:52
• Updated: 20/Nov/17 18:39
• Resolved: 04/May/16 13:05

Description

I have a test in which I make a 6-router network, then repeatedly kill and restart nodes.

To determine when the network is ready to rock, I send messages to each node that I expect to find in the network. All messages are sent through the one node that I am connected to.

At first, some of those messages are undeliverable. This is expected, since I just deliberately messed up the network.

the problem is that, for those undeliverables, I never get back any kind of disposition. for the good ones, i get 'settled'. for the undeliverable ones, i get nothing.

this means that i cannot close my session.
if i created the sender on it this way:
Sender sender = session.createSender("mgmt");
then it will not close.

I can work around the problem by creating the sender this way:
Sender sender = session.createSender("mgmt; {link:{reliability:unreliable}}");

...but we should still get back dispos for all messages.

Issue Links

• depends upon: DISPATCH-179 Refactor Router Core