You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Rafael Schloming <rh...@alum.mit.edu> on 2013/12/18 22:53:23 UTC
Proton 0.6 RC2
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/
Java binaries are available here:
https://repository.apache.org/content/repositories/orgapacheqpid-070/
--Rafael
Re: Proton 0.6 RC2
Posted by Ted Ross <tr...@redhat.com>.
Yes, it's fixed on trunk. Thanks!
-Ted
On 12/19/2013 05:52 AM, Rafael Schloming wrote:
> 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
>> 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: users-unsubscribe@qpid.apache.org
>>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
Re: Proton 0.6 RC2
Posted by Ted Ross <tr...@redhat.com>.
Yes, it's fixed on trunk. Thanks!
-Ted
On 12/19/2013 05:52 AM, Rafael Schloming wrote:
> 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
>> 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: users-unsubscribe@qpid.apache.org
>>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Proton 0.6 RC2
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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
> 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: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Proton 0.6 RC2
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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
> 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: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Proton 0.6 RC2
Posted by Frank Quinn <fq...@nyx.com>.
Sounds great, thanks Rafael - that one had been annoying us :).
Cheers,
Frank
----- Original Message -----
From: Rafael Schloming [mailto:rhs@alum.mit.edu]
Sent: Thursday, December 19, 2013 10:58 AM
To: proton@qpid.apache.org <pr...@qpid.apache.org>
Cc: users@qpid.apache.org <us...@qpid.apache.org>
Subject: Re: Proton 0.6 RC2
On Wed, Dec 18, 2013 at 6:43 PM, Frank Quinn <fq...@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 the PROTON-420 patch. I really don't
like adding a space to examples. I feel like it is pretty inevitable that
people will cut and paste example snippets and if there is an extra space
in there then it will lead to lots of problems. I do recall that there is
an alternative syntax for detailed comment descriptions in doxygen that
makes use of // style comments rather than /* style comments. I've switched
over to this form and removed the -Wno-comment from the build. This appears
to work for me, so hopefully it will fix your warnings also. SVN appears to
be down now, but I will check it in as soon as it is back up.
--Rafael
________________________________________________________
This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange Group, Inc. (ICE), NYSE Euronext or any of their subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.
________________________________________________________
Re: Proton 0.6 RC2
Posted by Rafael Schloming <rh...@alum.mit.edu>.
On Wed, Dec 18, 2013 at 6:43 PM, Frank Quinn <fq...@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 the PROTON-420 patch. I really don't
like adding a space to examples. I feel like it is pretty inevitable that
people will cut and paste example snippets and if there is an extra space
in there then it will lead to lots of problems. I do recall that there is
an alternative syntax for detailed comment descriptions in doxygen that
makes use of // style comments rather than /* style comments. I've switched
over to this form and removed the -Wno-comment from the build. This appears
to work for me, so hopefully it will fix your warnings also. SVN appears to
be down now, but I will check it in as soon as it is back up.
--Rafael
Re: Proton 0.6 RC2
Posted by Rafael Schloming <rh...@alum.mit.edu>.
On Wed, Dec 18, 2013 at 6:43 PM, Frank Quinn <fq...@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 the PROTON-420 patch. I really don't
like adding a space to examples. I feel like it is pretty inevitable that
people will cut and paste example snippets and if there is an extra space
in there then it will lead to lots of problems. I do recall that there is
an alternative syntax for detailed comment descriptions in doxygen that
makes use of // style comments rather than /* style comments. I've switched
over to this form and removed the -Wno-comment from the build. This appears
to work for me, so hopefully it will fix your warnings also. SVN appears to
be down now, but I will check it in as soon as it is back up.
--Rafael
Re: Proton 0.6 RC2
Posted by Frank Quinn <fq...@nyx.com>.
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.
Cheers,
Frank
----- Original Message -----
From: Rafael Schloming [mailto:rhs@alum.mit.edu]
Sent: Wednesday, December 18, 2013 10:49 PM
To: users@qpid.apache.org <us...@qpid.apache.org>
Cc: proton@qpid.apache.org <pr...@qpid.apache.org>
Subject: Re: Proton 0.6 RC2
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 <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
> 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: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
________________________________________________________
This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange Group, Inc. (ICE), NYSE Euronext or any of their subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.
________________________________________________________
Re: Proton 0.6 RC2
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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 <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
> 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: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Proton 0.6 RC2
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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 <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
> 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: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Proton 0.6 RC2
Posted by Ted Ross <tr...@redhat.com>.
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: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Proton 0.6 RC2
Posted by Ted Ross <tr...@redhat.com>.
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: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Proton 0.6 RC2
Posted by Ted Ross <tr...@redhat.com>.
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: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
Re: Proton 0.6 RC2
Posted by Ted Ross <tr...@redhat.com>.
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: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org