[
https://issues.apache.org/jira/browse/DISPATCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949143#comment-13949143
]
Pavel Moravec commented on DISPATCH-1:
--------------------------------------
Reopening the issue. Dispatch does not ever send disposition in the below
scenario:
1) Three dispatch routers inter-connected into a chain A<->B<->C.
2) A consumer attached on A:
drain --connection-options {protocol:amqp1.0} -f -b 0.0.0.0:20001 my_address
3) A producer connects to C and attempts to send message:
spout --connection-options {protocol:amqp1.0} -b 0.0.0.0:20003 -c 1 my_address
The producer is blocked forever, C router does not send disposition to the
transfer it received. C does not route the message towards B.
Adding "x-amqp-to=my_address" message property to send is a warkaround, anyway
the router should not hold the disposition forever any time.
> Use Target Address from the link if there is no To field in a message from a
> producer
> -------------------------------------------------------------------------------------
>
> Key: DISPATCH-1
> URL: https://issues.apache.org/jira/browse/DISPATCH-1
> Project: Qpid Dispatch
> Issue Type: Improvement
> Affects Versions: 0.1
> Reporter: Ted Ross
> Assignee: Ted Ross
> Fix For: 0.2
>
>
> When testing Dispatch against the Qpid messaging clients, messages are not
> properly forwarded because the clients use target.address instead of
> properties.to. Both cases should be supported by the router.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
