Description
An AMQP client attaches to an address with source address set to 'bar' and target address 'remote/foo1' (which the router does not know about):
[425203913:0] -> Attach{name='space2.bar.fwd2.out', handle=0, role=SENDER, sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='bar', durable=UNSETTLED_STATE, expiryPolicy=SESSION_END, timeout=0, dynamic=false, dynamicNodeProperties=null, distributionMode=null, filter=null, defaultOutcome=null, outcomes=null, capabilities=null}, target=Target{address='remote1/foo1', durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null}, unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0, maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null, properties=null}
As the router does not know about 'remote/foo1', it sets target=null, but also source address to 'null' (this is actually null, not the string 'null', proton-j is doing the formatting):
[425203913:0] <- Attach{name='space2.bar.fwd2.out', handle=0, role=RECEIVER, sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null', durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false, dynamicNodeProperties=null, distributionMode=null, filter=null, defaultOutcome=null, outcomes=null, capabilities=null}, target=null, unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0, maxMessageSize=0, offeredCapabilities=null, desiredCapabilities=null, properties=null} [425203913:0] <- Detach{handle=0, closed=true, error=Error{condition=qd:no-route-to-dest, description='No route to the destination node', info=null}}
This can be handled in client code, but the question is if the router should keep address='bar' in the replied attach or not.
Possibly related: https://issues.apache.org/jira/browse/DISPATCH-962 (CC robbie)