I believe I've fixed this on trunk. Let me know if you still see the
problem there.
--Rafael
On Wed, Dec 18, 2013 at 5:44 PM, Ted Ross tr...@redhat.com wrote:
Digging further into this, I see that Messenger is providing the
subscription and the address before the dynamic-attach handshake is
On Wed, Dec 18, 2013 at 6:43 PM, Frank Quinn fqu...@nyx.com wrote:
Hi Rafael,
Could we get PROTON-420 in there too? I attached a patch to the ticket
which fixes, it's just for compiler warning prevention when compiling
against proton with strict flags.
I have applied a modified version of
...@qpid.apache.org
Subject: Re: Proton 0.6 RC2
On Wed, Dec 18, 2013 at 6:43 PM, Frank Quinn fqu...@nyx.com wrote:
Hi Rafael,
Could we get PROTON-420 in there too? I attached a patch to the ticket
which fixes, it's just for compiler warning prevention when compiling
against proton with strict flags.
I have
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:
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
