You're right, the address accessor is supposed to block until the address is available. It certainly looks like it's not doing that. I'll try to reproduce locally or failing that produce a debugging patch for you to try in your environment.
--Rafael On Wed, Dec 18, 2013 at 5:44 PM, Ted Ross <[email protected]> wrote: > Digging further into this, I see that Messenger is providing the > subscription and the address before the dynamic-attach handshake is > completed. It was my understanding that one or both of those calls would > block until the name was resolved. > > -Ted > > > On 12/18/2013 05:25 PM, Ted Ross wrote: > >> QPID-439 seems to have reverted in this RC. >> >> Here's my client code: >> >> self.M.route("amqp:/*", "amqp://%s/$1" % host) >> self.subscription = self.M.subscribe("amqp:/#") >> self.reply = self.subscription.address >> print "REPLY:", self.reply >> >> The output is: >> >> REPLY: None >> >> yet the trace looks like this: >> >> [0x26135e0]:0 -> @attach(18) [name="receiver-xxx", handle=0, >> role=true, snd-settle-mode=2, rcv-settle-mode=0, >> source=@source(40) [durable=0, timeout=0, dynamic=true], >> target=@target(41) [durable=0, timeout=0, dynamic=false], >> initial-delivery-count=0] >> [0x26135e0]:0 <- @attach(18) [name="receiver-xxx", handle=0, >> role=false, snd-settle-mode=2, rcv-settle-mode=0, >> source=@source(40) [address="amqp:/_topo/0/ >> Router.A/temp.4TQT_a", >> durable=0, timeout=0, dynamic=true], initial-delivery-count=0] >> >> >> >> On 12/18/2013 04:53 PM, Rafael Schloming wrote: >> >>> Hi Everyone, >>> >>> I've just posted proton 0.6 RC2. The changes since RC1 are listed in the >>> attached file. Please check it out and let me know if you run into any >>> issues. >>> >>> Sources are available here: >>> >>> http://people.apache.org/~rhs/qpid-proton-0.6rc2/ < >>> http://people.apache.org/%7Erhs/qpid-proton-0.6rc2/> >>> >>> Java binaries are available here: >>> >>> https://repository.apache.org/content/repositories/orgapacheqpid-070/ >>> >>> --Rafael >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
