----- Original Message ----- > From: "Olivier Mallassi" <[email protected]> > To: "Alan Conway" <[email protected]> > Cc: "Rob Godfrey" <[email protected]>, [email protected], > [email protected] > Sent: Saturday, April 8, 2017 8:04:17 AM > Subject: Re: Configuring addresses starting with '/' on qpid-dispatch router > 0.7.0 > > So following your idea, I am now trying to connect client. > > python simpleSend.py -a amqp://localhost:20202//domain/subdomain/queue1 -m > 10000 (note the //) > on the client, I see the attach frame > > @attach(18) > [name="71e559bd-81f1-4512-9223-d226aa813bb7-/domain/subdomain/queue1", > handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0, > source=@source(40) [durable=0, timeout=0, dynamic=false], > target=@target(41) [address="/domain/subdomain/queue1", durable=0, > timeout=0, dynamic=false], initial-delivery-count=0, max-message-size=0] > > > yet, usind qdstat > > qdstat -b localhost:20202 -a > Router Addresses > class addr phs distrib in-proc local remote > cntnr in out thru to-proc from-proc > > =================================================================================================================== > local $_management_internal closest 1 0 0 > 0 0 0 0 0 0 > mobile $management 0 closest 1 0 0 > 0 2 0 0 2 0 > local $management closest 1 0 0 > 0 0 0 0 0 0 > mobile */domain*/subdomain/queue1 1 balanced 0 0 0 > 0 0 0 0 0 0 > mobile */domain*/subdomain/queue1 0 balanced 0 1 0 > 0 0 0 0 0 0 > mobile *domain/*subdomain/queue1 0 balanced 0 0 0 > 0 0 0 0 0 0 > local temp.k1lchlMcGRfNM3N balanced 0 1 0 > 0 0 0 0 0 0 > > > note the /domain are created via autoLink (following the Alan's idea of > ////) > > the third one (domain/subdomain w/o the first /) is created (and deleted) > when starting the python client (and stopping it). > > Looks like the dispatch router is also normalizing incoming Adress > (independently of the number of /// by the way ;) ) The router does normalize incoming addresses. Here is the code that does that -
https://github.com/apache/qpid-dispatch/blob/master/src/router_core/connections.c#L1061 >From what I can see, the router remives a maximum of 3 leading slashes. So, if you run a simple_send on the router like this - python simple_recv.py -m1 --address localhost////examples, the router stores /examples in its address table. If you have the following auto link in your config file, the address pulp gets address table - autoLink { addr: ///pulp connection: broker dir: in } We will have to come up with a comprehensive solution to the problem of leading slashes. > > On Fri, Apr 7, 2017 at 10:48 PM, Olivier Mallassi < > [email protected]> wrote: > > > Crafty :) > > > > I have just ran quick tests and it helps establishing the link between the > > dispatch & broker (attach flow frames) > > I am yet not able to send messages (got the attach frame by the client get > > stuck) I have to digg into > > > > Do you want me to create a Jira on this? > > > > Thx > > > > > > > > On Fri, 7 Apr 2017 at 17:38, Alan Conway <[email protected]> wrote: > > > >> On Fri, 2017-04-07 at 17:08 +0200, Olivier Mallassi wrote: > >> > > >> > I am fine with the "//" as long as it is not considered as connection > >> > information :) > >> > > >> > >> Random thought: have you tried "////addr" in the configuration file? > >> > >> "//" + "" + "/" + "/addr" == "/addr" > >> > >> I haven't tried it, I may be dreaming. It is definitely not the > >> solution, but maybe a useful temporary workaround. > >> > >> > > I think Ganesh is already working on that so I'll stop confusing > >> > > the > >> > > issue. > >> > > > >> > > > >> > > > >> > > >> > > >> > Let us know if this is the case, that would be great!! > >> > > >> > >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
