Hi Gordon,
I tried this independently and this is just to report I get the same results
as Richard.
I had a consumer with an address
"myqueue; {create: receiver, node: {x-declare: {arguments:
{'qpid.policy_type': ring, 'qpid.max_size': 500000000}}, x-bindings:
[{exchange: 'amq.match', queue: 'myqueue', key: 'data1', arguments:
{x-match: any, data-service: item-selection, item-owner: fadams}}]}}"
My test producer runs 1000 iterations, every message has
data-service=item-selection set and I've got a line
if ((i % 3) == 0) message.setStringProperty("item-owner", "fadams");
else message.setStringProperty("item-owner", "jdadams");
to twiddle with item-owner just to see what happens.
I did qpid-route dynamic add localhost:5673 localhost:5672 amq.match
And my consumer counted 1666 items!!!!!! clearly I was expecting 1000 given
an x-match any - my address has key: 'data1' in the x-bindings.
I'm running 0.10 brokers
So it doesn't look like the binding key suggestion works.
I guess if your trunk version also includes your "x-match:all" fix perhaps
there's something in there that sorts out the duplicates issue too?
Regards
Frase.
Gordon Sim wrote:
>
> On 07/15/2011 04:43 PM, Fallon, Richard wrote:
>> FYI - I have tried adding unique keys to each of the subscribers but
>> unfortunately still get the same results.
>
> Hmmm... it worked for me (albeit on trunk, but I don't *think* that
> should make a difference here).
>
>
>
--
View this message in context:
http://apache-qpid-users.2158936.n2.nabble.com/Dynamic-Routes-and-Duplicate-Messages-tp6562267p6587695.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
