You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by "Fallon, Richard" <ri...@atosorigin.com> on 2011/06/06 18:13:40 UTC
Dynamic Routes with the Headers Exchange
All,
I have been happily using federated brokers linked via dynamic routes
using the topic exchange. As you know this allows me to publish to one
broker and subscribe to that data from another, great!
However I have recently switched to using the headers exchange for
subscriptions, but am unable to subscribe to data from a dynamic route.
So I have
SRC_BROKER linked to a DEST_BROKER
FYI
1) I can successfully publish to amq.match on SRC_BROKER and subscribe
to the same broker using the (rather lengthy but powerful) amqp headers
syntax
This tells me I am using the right publish subscribe syntax.
2) I then set up the dynamic route, linked using the command
qpid-route add dynamic DEST_BROKER SRC_BROKER amq.match
3) But I cannot subscribe to the same messages on the DEST_BROKER
despite having set up the dynamic route.
4) However I can subscribe to messages on the DEST_BROKER that have
been published to the SRC_BROKER on the topic exchange
This tells me I can (at least) connect the brokers on the topic
exchange
So the first simple question - can I use dynamic routes with the headers
exchange?
I'm using Qpid-0.8 c++ broker.
Thanks as ever
Richard Fallon
_______________________________________________________
Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
_______________________________________________________
RE: Dynamic Routes with the Headers Exchange
Posted by "Fallon, Richard" <ri...@atosorigin.com>.
Wow, that's good work!
I'll keep an eye on progress.
-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com]
Sent: 09 June 2011 13:51
To: users@qpid.apache.org
Subject: Re: Dynamic Routes with the Headers Exchange
On 06/09/2011 01:44 PM, Fallon, Richard wrote:
>
> Hi Gordon,
>
> Thanks for taking the time to look at this.
>
> Rather unfortunately our whole design has been centered around the use
> of dynamic routes and the header exchange, however at this stage 'any'
> is better than 'none'! And at least I know I'm not going insane!
>
> So, I've never been in this position before where I am
> interested/relying on a fix. What are the usual kind of timescales
> for such a fix?
I've pasted in a suggested fix to the JIRA[1]. It passes all existing
tests and seems to fix my test case. However I'd like to get a bit more
review from those more familiar with the code before committing.
Once committed it would then be part of the next release, which is 0.12
targeted for the end of July. You could of course apply the patch to the
0.10 release yourself before that.
--Gordon.
[1] https://issues.apache.org/jira/browse/QPID-3298
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
_______________________________________________________
Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
_______________________________________________________
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: Dynamic Routes with the Headers Exchange
Posted by "Fallon, Richard" <ri...@atosorigin.com>.
Thanks, in fact in our environment the source is the harder one to
maintain anyway. So will upgrade destination broker at the same time as
the source brokers.
-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com]
Sent: 13 June 2011 15:11
To: users@qpid.apache.org
Subject: Re: Dynamic Routes with the Headers Exchange
On 06/13/2011 03:09 PM, Fallon, Richard wrote:
> Will the fix you have submitted need to be applied to the source
> broker, destination broker or both?
Strictly, only the source broker would require it (assuming
uni-directional routing). However it might save troubleshooting time to
apply to both.
> -----Original Message-----
> From: Gordon Sim [mailto:gsim@redhat.com]
> Sent: 09 June 2011 16:41
> To: users@qpid.apache.org
> Subject: Re: Dynamic Routes with the Headers Exchange
>
> On 06/09/2011 01:50 PM, Gordon Sim wrote:
>> On 06/09/2011 01:44 PM, Fallon, Richard wrote:
>>>
>>> Hi Gordon,
>>>
>>> Thanks for taking the time to look at this.
>>>
>>> Rather unfortunately our whole design has been centered around the
>>> use of dynamic routes and the header exchange, however at this stage
> 'any'
>>> is better than 'none'! And at least I know I'm not going insane!
>>>
>>> So, I've never been in this position before where I am
>>> interested/relying on a fix. What are the usual kind of timescales
>>> for such a fix?
>>
>> I've pasted in a suggested fix to the JIRA[1]. It passes all existing
>> tests and seems to fix my test case. However I'd like to get a bit
>> more review from those more familiar with the code before committing.
>>
>> Once committed it would then be part of the next release, which is
>> 0.12 targeted for the end of July. You could of course apply the
>> patch
>
>> to the 0.10 release yourself before that.
>
> FYI: fix (and new test) committed as r1133942.
>
>> --Gordon.
>>
>> [1] https://issues.apache.org/jira/browse/QPID-3298
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
>
>
> _______________________________________________________
> Atos Origin and Atos Consulting are trading names used by the Atos
> Origin group. The following trading entities are registered in
> England and Wales: Atos Origin IT Services UK Limited (registered
> number 01245534) and Atos Consulting Limited (registered number
> 04312380). The registered office for each is at 4 Triton Square,
> Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
>
> This e-mail and the documents attached are confidential and intended
solely for the addressee, and may contain confidential or privileged
information. If you receive this e-mail in error, you are not
authorised to copy, disclose, use or retain it. Please notify the
sender immediately and delete this email from your systems. As emails
may be intercepted, amended or lost, they are not secure. Atos Origin
therefore can accept no liability for any errors or their content.
Although Atos Origin endeavours to maintain a virus-free network, we do
not warrant that this transmission is virus-free and can accept no
liability for any damages resulting from any virus transmitted. The
risks are deemed to be accepted by everyone who communicates with Atos
Origin by email.
> _______________________________________________________
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
_______________________________________________________
Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
_______________________________________________________
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Dynamic Routes with the Headers Exchange
Posted by Gordon Sim <gs...@redhat.com>.
On 06/13/2011 03:09 PM, Fallon, Richard wrote:
> Will the fix you have submitted need to be applied to the source broker,
> destination broker or both?
Strictly, only the source broker would require it (assuming
uni-directional routing). However it might save troubleshooting time to
apply to both.
> -----Original Message-----
> From: Gordon Sim [mailto:gsim@redhat.com]
> Sent: 09 June 2011 16:41
> To: users@qpid.apache.org
> Subject: Re: Dynamic Routes with the Headers Exchange
>
> On 06/09/2011 01:50 PM, Gordon Sim wrote:
>> On 06/09/2011 01:44 PM, Fallon, Richard wrote:
>>>
>>> Hi Gordon,
>>>
>>> Thanks for taking the time to look at this.
>>>
>>> Rather unfortunately our whole design has been centered around the
>>> use of dynamic routes and the header exchange, however at this stage
> 'any'
>>> is better than 'none'! And at least I know I'm not going insane!
>>>
>>> So, I've never been in this position before where I am
>>> interested/relying on a fix. What are the usual kind of timescales
>>> for such a fix?
>>
>> I've pasted in a suggested fix to the JIRA[1]. It passes all existing
>> tests and seems to fix my test case. However I'd like to get a bit
>> more review from those more familiar with the code before committing.
>>
>> Once committed it would then be part of the next release, which is
>> 0.12 targeted for the end of July. You could of course apply the patch
>
>> to the 0.10 release yourself before that.
>
> FYI: fix (and new test) committed as r1133942.
>
>> --Gordon.
>>
>> [1] https://issues.apache.org/jira/browse/QPID-3298
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
>
>
> _______________________________________________________
> Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
>
> This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
> _______________________________________________________
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: Dynamic Routes with the Headers Exchange
Posted by "Fallon, Richard" <ri...@atosorigin.com>.
Gordon,
One more thing.
Will the fix you have submitted need to be applied to the source broker,
destination broker or both?
Richard
-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com]
Sent: 09 June 2011 16:41
To: users@qpid.apache.org
Subject: Re: Dynamic Routes with the Headers Exchange
On 06/09/2011 01:50 PM, Gordon Sim wrote:
> On 06/09/2011 01:44 PM, Fallon, Richard wrote:
>>
>> Hi Gordon,
>>
>> Thanks for taking the time to look at this.
>>
>> Rather unfortunately our whole design has been centered around the
>> use of dynamic routes and the header exchange, however at this stage
'any'
>> is better than 'none'! And at least I know I'm not going insane!
>>
>> So, I've never been in this position before where I am
>> interested/relying on a fix. What are the usual kind of timescales
>> for such a fix?
>
> I've pasted in a suggested fix to the JIRA[1]. It passes all existing
> tests and seems to fix my test case. However I'd like to get a bit
> more review from those more familiar with the code before committing.
>
> Once committed it would then be part of the next release, which is
> 0.12 targeted for the end of July. You could of course apply the patch
> to the 0.10 release yourself before that.
FYI: fix (and new test) committed as r1133942.
> --Gordon.
>
> [1] https://issues.apache.org/jira/browse/QPID-3298
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
_______________________________________________________
Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
_______________________________________________________
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: Dynamic Routes with the Headers Exchange
Posted by "Fallon, Richard" <ri...@atosorigin.com>.
Gordon,
Amazing - that's very good service indeed. I've already sung your
praises to a number of friends and colleagues.
Thanks very much
Richard
-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com]
Sent: 09 June 2011 16:41
To: users@qpid.apache.org
Subject: Re: Dynamic Routes with the Headers Exchange
On 06/09/2011 01:50 PM, Gordon Sim wrote:
> On 06/09/2011 01:44 PM, Fallon, Richard wrote:
>>
>> Hi Gordon,
>>
>> Thanks for taking the time to look at this.
>>
>> Rather unfortunately our whole design has been centered around the
>> use of dynamic routes and the header exchange, however at this stage
'any'
>> is better than 'none'! And at least I know I'm not going insane!
>>
>> So, I've never been in this position before where I am
>> interested/relying on a fix. What are the usual kind of timescales
>> for such a fix?
>
> I've pasted in a suggested fix to the JIRA[1]. It passes all existing
> tests and seems to fix my test case. However I'd like to get a bit
> more review from those more familiar with the code before committing.
>
> Once committed it would then be part of the next release, which is
> 0.12 targeted for the end of July. You could of course apply the patch
> to the 0.10 release yourself before that.
FYI: fix (and new test) committed as r1133942.
> --Gordon.
>
> [1] https://issues.apache.org/jira/browse/QPID-3298
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
_______________________________________________________
Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
_______________________________________________________
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Dynamic Routes with the Headers Exchange
Posted by Gordon Sim <gs...@redhat.com>.
On 06/09/2011 01:50 PM, Gordon Sim wrote:
> On 06/09/2011 01:44 PM, Fallon, Richard wrote:
>>
>> Hi Gordon,
>>
>> Thanks for taking the time to look at this.
>>
>> Rather unfortunately our whole design has been centered around the use
>> of dynamic routes and the header exchange, however at this stage 'any'
>> is better than 'none'! And at least I know I'm not going insane!
>>
>> So, I've never been in this position before where I am
>> interested/relying on a fix. What are the usual kind of timescales for
>> such a fix?
>
> I've pasted in a suggested fix to the JIRA[1]. It passes all existing
> tests and seems to fix my test case. However I'd like to get a bit more
> review from those more familiar with the code before committing.
>
> Once committed it would then be part of the next release, which is 0.12
> targeted for the end of July. You could of course apply the patch to the
> 0.10 release yourself before that.
FYI: fix (and new test) committed as r1133942.
> --Gordon.
>
> [1] https://issues.apache.org/jira/browse/QPID-3298
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Dynamic Routes with the Headers Exchange
Posted by Gordon Sim <gs...@redhat.com>.
On 06/09/2011 01:44 PM, Fallon, Richard wrote:
>
> Hi Gordon,
>
> Thanks for taking the time to look at this.
>
> Rather unfortunately our whole design has been centered around the use
> of dynamic routes and the header exchange, however at this stage 'any'
> is better than 'none'! And at least I know I'm not going insane!
>
> So, I've never been in this position before where I am
> interested/relying on a fix. What are the usual kind of timescales for
> such a fix?
I've pasted in a suggested fix to the JIRA[1]. It passes all existing
tests and seems to fix my test case. However I'd like to get a bit more
review from those more familiar with the code before committing.
Once committed it would then be part of the next release, which is 0.12
targeted for the end of July. You could of course apply the patch to the
0.10 release yourself before that.
--Gordon.
[1] https://issues.apache.org/jira/browse/QPID-3298
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: Dynamic Routes with the Headers Exchange
Posted by "Fallon, Richard" <ri...@atosorigin.com>.
Hi Gordon,
Thanks for taking the time to look at this.
Rather unfortunately our whole design has been centered around the use
of dynamic routes and the header exchange, however at this stage 'any'
is better than 'none'! And at least I know I'm not going insane!
So, I've never been in this position before where I am
interested/relying on a fix. What are the usual kind of timescales for
such a fix?
Richard
-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com]
Sent: 09 June 2011 12:43
To: users@qpid.apache.org
Subject: Re: Dynamic Routes with the Headers Exchange
On 06/09/2011 10:02 AM, Fallon, Richard wrote:
>
>
> Hello all,
>
> Can anyone confirm if I can use dynamic routes with the headers
> exchange in Qpid 0.8 c++ broker?
It is certainly expected to work now. There are a handful of automated
tests for that case that were added in at
http://svn.apache.org/viewvc?view=revision&revision=905322 along with
some fixes and the 0.8 release branch was taken from r1032357.
However I was also unable to get a simple test to work. It looks like
x-match:all does not work while x-match:any does (and only the second
case is tested for at present). I've raised a new JIRA for that (could
also just reopen the original JIRA).
>
> As per previous mail I am unable to get it to work, and am wondering
> if it is possible, if I am doing something wrong or maybe need to
> upgrade versions?
>
> Thanks
>
> Richard
>
>> _____________________________________________
>> From: Fallon, Richard
>> Sent: 06 June 2011 17:14
>> To: users@qpid.apache.org
>> Subject: Dynamic Routes with the Headers Exchange
>>
>>
>>
>> All,
>>
>> I have been happily using federated brokers linked via dynamic routes
>> using the topic exchange. As you know this allows me to publish to
>> one broker and subscribe to that data from another, great!
>>
>> However I have recently switched to using the headers exchange for
>> subscriptions, but am unable to subscribe to data from a dynamic
>> route.
>>
>> So I have
>>
>> SRC_BROKER linked to a DEST_BROKER
>>
>>
>>
>> FYI
>>
>> 1) I can successfully publish to amq.match on SRC_BROKER and
>> subscribe to the same broker using the (rather lengthy but powerful)
>> amqp headers syntax
>> This tells me I am using the right publish subscribe syntax.
>>
>> 2) I then set up the dynamic route, linked using the command
>> qpid-route add dynamic DEST_BROKER SRC_BROKER amq.match
>>
>> 3) But I cannot subscribe to the same messages on the DEST_BROKER
>> despite having set up the dynamic route.
>>
>> 4) However I can subscribe to messages on the DEST_BROKER that have
>> been published to the SRC_BROKER on the topic exchange
>> This tells me I can (at least) connect the brokers on the topic
>> exchange
>>
>>
>> So the first simple question - can I use dynamic routes with the
>> headers exchange?
>>
>> I'm using Qpid-0.8 c++ broker.
>>
>> Thanks as ever
>>
>> Richard Fallon
>
>
> _______________________________________________________
> Atos Origin and Atos Consulting are trading names used by the Atos
> Origin group. The following trading entities are registered in
> England and Wales: Atos Origin IT Services UK Limited (registered
> number 01245534) and Atos Consulting Limited (registered number
> 04312380). The registered office for each is at 4 Triton Square,
> Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
>
> This e-mail and the documents attached are confidential and intended
solely for the addressee, and may contain confidential or privileged
information. If you receive this e-mail in error, you are not
authorised to copy, disclose, use or retain it. Please notify the
sender immediately and delete this email from your systems. As emails
may be intercepted, amended or lost, they are not secure. Atos Origin
therefore can accept no liability for any errors or their content.
Although Atos Origin endeavours to maintain a virus-free network, we do
not warrant that this transmission is virus-free and can accept no
liability for any damages resulting from any virus transmitted. The
risks are deemed to be accepted by everyone who communicates with Atos
Origin by email.
> _______________________________________________________
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
_______________________________________________________
Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
_______________________________________________________
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Dynamic Routes with the Headers Exchange
Posted by Gordon Sim <gs...@redhat.com>.
On 06/09/2011 10:02 AM, Fallon, Richard wrote:
>
>
> Hello all,
>
> Can anyone confirm if I can use dynamic routes with the headers exchange
> in Qpid 0.8 c++ broker?
It is certainly expected to work now. There are a handful of automated
tests for that case that were added in at
http://svn.apache.org/viewvc?view=revision&revision=905322 along with
some fixes and the 0.8 release branch was taken from r1032357.
However I was also unable to get a simple test to work. It looks like
x-match:all does not work while x-match:any does (and only the second
case is tested for at present). I've raised a new JIRA for that (could
also just reopen the original JIRA).
>
> As per previous mail I am unable to get it to work, and am wondering if
> it is possible, if I am doing something wrong or maybe need to upgrade
> versions?
>
> Thanks
>
> Richard
>
>> _____________________________________________
>> From: Fallon, Richard
>> Sent: 06 June 2011 17:14
>> To: users@qpid.apache.org
>> Subject: Dynamic Routes with the Headers Exchange
>>
>>
>>
>> All,
>>
>> I have been happily using federated brokers linked via dynamic routes
>> using the topic exchange. As you know this allows me to publish to
>> one broker and subscribe to that data from another, great!
>>
>> However I have recently switched to using the headers exchange for
>> subscriptions, but am unable to subscribe to data from a dynamic
>> route.
>>
>> So I have
>>
>> SRC_BROKER linked to a DEST_BROKER
>>
>>
>>
>> FYI
>>
>> 1) I can successfully publish to amq.match on SRC_BROKER and subscribe
>> to the same broker using the (rather lengthy but powerful) amqp
>> headers syntax
>> This tells me I am using the right publish subscribe syntax.
>>
>> 2) I then set up the dynamic route, linked using the command
>> qpid-route add dynamic DEST_BROKER SRC_BROKER amq.match
>>
>> 3) But I cannot subscribe to the same messages on the DEST_BROKER
>> despite having set up the dynamic route.
>>
>> 4) However I can subscribe to messages on the DEST_BROKER that have
>> been published to the SRC_BROKER on the topic exchange
>> This tells me I can (at least) connect the brokers on the topic
>> exchange
>>
>>
>> So the first simple question - can I use dynamic routes with the
>> headers exchange?
>>
>> I'm using Qpid-0.8 c++ broker.
>>
>> Thanks as ever
>>
>> Richard Fallon
>
>
> _______________________________________________________
> Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
>
> This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
> _______________________________________________________
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
RE: Dynamic Routes with the Headers Exchange
Posted by "Fallon, Richard" <ri...@atosorigin.com>.
Hello all,
Can anyone confirm if I can use dynamic routes with the headers exchange
in Qpid 0.8 c++ broker?
As per previous mail I am unable to get it to work, and am wondering if
it is possible, if I am doing something wrong or maybe need to upgrade
versions?
Thanks
Richard
> _____________________________________________
> From: Fallon, Richard
> Sent: 06 June 2011 17:14
> To: users@qpid.apache.org
> Subject: Dynamic Routes with the Headers Exchange
>
>
>
> All,
>
> I have been happily using federated brokers linked via dynamic routes
> using the topic exchange. As you know this allows me to publish to
> one broker and subscribe to that data from another, great!
>
> However I have recently switched to using the headers exchange for
> subscriptions, but am unable to subscribe to data from a dynamic
> route.
>
> So I have
>
> SRC_BROKER linked to a DEST_BROKER
>
>
>
> FYI
>
> 1) I can successfully publish to amq.match on SRC_BROKER and subscribe
> to the same broker using the (rather lengthy but powerful) amqp
> headers syntax
> This tells me I am using the right publish subscribe syntax.
>
> 2) I then set up the dynamic route, linked using the command
> qpid-route add dynamic DEST_BROKER SRC_BROKER amq.match
>
> 3) But I cannot subscribe to the same messages on the DEST_BROKER
> despite having set up the dynamic route.
>
> 4) However I can subscribe to messages on the DEST_BROKER that have
> been published to the SRC_BROKER on the topic exchange
> This tells me I can (at least) connect the brokers on the topic
> exchange
>
>
> So the first simple question - can I use dynamic routes with the
> headers exchange?
>
> I'm using Qpid-0.8 c++ broker.
>
> Thanks as ever
>
> Richard Fallon
_______________________________________________________
Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983
This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email.
_______________________________________________________