Thanks Andy, that helped a lot.
I have been trying to get the federation to work. I have setup a simple
scenario with 3 brokers ( and for the time being on one host using different
port numbers when starting the brokers). It is a simple broker node
configuration i.e. 3 is connected to 2 which is connected to 4 ; 3 2 4 in line
so to speak.
I have configured bidirectional links from 3 to 2 and also from 2 to 4 ( 3 <==>
2, 2 <==> 4 ) using the qpid-route tool and adding dynamic routes using the
amq.topic as the exchange, so it looks like this
3<=======>2<========>4
Then I start consumers using the "drain" application from the release on all
the brokers, 3, 2 and 4.
./drain amq.topic -t 1000 -b localhost:5672 on 2
./drain amq.topic -t 1000 -b localhost:5673 on 3
./drain amq.topic -t 1000 -b localhost:5674 on 4
I used the "spout" application to send message to the localhost:5672 broker.
I expect all 3 consumers to get the message. What happens is that only 2 get
it, in this case broker 2 and broker 4.
3 never gets one.
If I send it to 3, only 3 and 2 get it.
If I send it to 4, only 4 and 2 get it.
It seems like only 2 brokers get it. It only seems to send it to 2
destinations.
This I proved by stopping one of the receivers, for example receiver on broker
3. In that case 2 and 4 get the messages now. The limit seems to be 2.
Can someone help me understand what is happening?
We really like the concept of federations for what we want to do, but this is a
road block.
Of course I could be doing something totally incorrect, then please accept my
applogies, but I would appreciate a explanation.
Thanks
Nitin
-----Original Message-----
From: Andy Goldstein [mailto:[email protected]]
Sent: Wednesday, June 06, 2012 9:41 AM
To: [email protected]
Subject: Re: qpid-route tool
Hi Nitin,
Do you happen to have the python-qpid-qmf RPM installed by any chance, version
0.14-*, or the python QMF library from 0.14? The issue you're running into is
because the qmf.console package (which contains the addBroker method) was
updated for 0.16 to allow you to specify **kwargs, but it looks like the
version that python is finding on your system is still the old one.
Andy
On Jun 6, 2012, at 8:29 AM, Nitin Shah wrote:
> This is the message I had sent out 2 days ago. Can someone guide me .
>
> I am running the 0-16 C_++ broker and issuing this command gives this error.
> Can someone point me to what is going on.
>
> qpid-route link list
> Failed: TypeError - addBroker() got an unexpected keyword argument
> 'client_properties'
>
> Thanks
> Nitin
>
>
> ========== Previous message ================ _______ Hi Guys,
>
> The version 0-16 of the tool qpid-route utility does not seem to work . I
> sent the message out yesterday, but no one responded. I ran the version 0-14
> of the tools release against 0-16 broker and that seems to at least come back
> with a reasonable answer. Can someone answer what action am I supposed to
> take to fix this problem?
>
> Thanks
>
> Nitin
>
> [cid:[email protected]]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional
commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
