[
https://issues.apache.org/jira/browse/DISPATCH-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-32.
------------------------------
Resolution: Fixed
I claim that this issue is resolved in 0.6.0. It would be good to retest this
scenario.
> Undeliverable messages should get released.
> -------------------------------------------
>
> Key: DISPATCH-32
> URL: https://issues.apache.org/jira/browse/DISPATCH-32
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 0.2
> Environment: cold, snowy.
> Reporter: michael goulish
> Assignee: Ted Ross
> Fix For: 0.6
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
