You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lance Doran (JIRA)" <ji...@apache.org> on 2012/11/18 20:10:57 UTC
[jira] [Updated] (QPID-4442) x-match fails to match properties
[ https://issues.apache.org/jira/browse/QPID-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lance Doran updated QPID-4442:
------------------------------
Description:
Using the spout/drain messaging example. I run the spout like this:
spout -P source:sports -c 1 my_exchange
And I run drain like this:
drain -f "my_queue; {create:receiver, node:{x-declare:{auto-delete:true},x-bindings:[{exchange:'my_exchange',queue:'my_queue,key:'key',arguments:{x-match:any,source:'sports'}}]}}"
Using a drain built on version v0.14, this works, the source property is correctly matched and messages are correctly routed to the drain through a v0.18 C++ broker; using a drain built in version v0.18, messages are not routed to the drain's queue.
Further inspection (at the packet level) shows that the difference is that in the exchange.bind method on the drain side, 'sports' is encoded as a variable binary (0x90) in v0.14, but a string (0x95) in v0.18.
was:
Using the spout/drain messaging example. I run the spout like this:
spout -P source:sports -c 1 my_exchange
And I run drain like this:
drain -f "my_queue; {create:receiver, node:{x-declare:{auto-delete:true},x-bindings:[{exchange:'my_exchange',queue:'my_queue,key:'key',arguments:{x-match:any,source:'sports'}}]}}"
Using a drain built on version v0.14, this works and messages are correctly routed to the drain through the v0.18 C++ broker; using a drain built in version v0.18, messages not.
Further inspection (at the packet level) shows that the difference is that in the exchange.bind method on the drain side, 'sports' is encoded as a variable binary (0x90) in v0.14, but a string (0x95) in v0.18.
> x-match fails to match properties
> ---------------------------------
>
> Key: QPID-4442
> URL: https://issues.apache.org/jira/browse/QPID-4442
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.18
> Environment: CentOS 6.2
> Reporter: Lance Doran
> Fix For: 0.19
>
>
> Using the spout/drain messaging example. I run the spout like this:
> spout -P source:sports -c 1 my_exchange
> And I run drain like this:
> drain -f "my_queue; {create:receiver, node:{x-declare:{auto-delete:true},x-bindings:[{exchange:'my_exchange',queue:'my_queue,key:'key',arguments:{x-match:any,source:'sports'}}]}}"
> Using a drain built on version v0.14, this works, the source property is correctly matched and messages are correctly routed to the drain through a v0.18 C++ broker; using a drain built in version v0.18, messages are not routed to the drain's queue.
> Further inspection (at the packet level) shows that the difference is that in the exchange.bind method on the drain side, 'sports' is encoded as a variable binary (0x90) in v0.14, but a string (0x95) in v0.18.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org