Adel,
How are you sending the messages? In my test, I used simple_send.py to
send 500 messages. It looks like you've got everything set up correctly.
-Ted
On 05/24/2016 08:03 AM, Adel Boutros wrote:
*a/fter the autolinks are activated/*
*qdstat -a*
Router Addresses
class addr phs distrib in-proc local remote
cntnr in out thru to-proc from-proc
=================================================================================================================
local $_management_internal closest 1 0 0 0
0 0 0 5 5
local $displayname closest 1 0 0 0
0 0 0 0 0
mobile $management 0 closest 1 0 0 0
16 0 0 16 0
local $management closest 1 0 0 0
0 0 0 0 0
mobile cluster.queue 1 balanced 0 0 0 0
0 0 0 0 0
mobile cluster.queue 0 balanced 0 2 0 0
0 0 0 0 0
local qdhello flood 1 0 0 0
0 0 0 0 3
local qdrouter flood 1 0 0 0
0 0 0 0 0
topo qdrouter flood 1 0 0 0
0 0 0 0 5
local qdrouter.ma multicast 1 0 0 0
0 0 0 0 0
topo qdrouter.ma multicast 1 0 0 0
0 0 0 0 1
local temp.cMDIgz6YT1MOtQh closest 0 1 0 0
0 0 0 0 0
*qdstat -l*
Router Links
type dir conn id id peer class addr phs cap
undel unsettled deliveries admin oper
=======================================================================================================================
endpoint in 8 19 mobile cluster.queue 1 250
0 0 0 enabled up
endpoint out 8 23 mobile cluster.queue 0 250
0 0 0 enabled up
endpoint in 15 35 mobile cluster.queue 1 250
0 0 0 enabled up
endpoint out 15 39 mobile cluster.queue 0 250
0 0 0 enabled up
endpoint in 19 42 mobile $management 0 250
0 0 1 enabled up
endpoint out 19 43 local temp.l5S7mNoIVvYZa5Q 250
0 0 0 enabled up
*/after the test is run/*
*qdstat -a*
Router Addresses
class addr phs distrib in-proc local remote
cntnr in out thru to-proc from-proc
==================================================================================================================
local $_management_internal closest 1 0 0 0
0 0 0 5 5
local $displayname closest 1 0 0 0
0 0 0 0 0
mobile $management 0 closest 1 0 0 0
18 0 0 18 0
local $management closest 1 0 0 0
0 0 0 0 0
mobile cluster.queue 1 balanced 0 0 0 0
500 500 0 0 0
mobile cluster.queue 0 balanced 0 2 0 0
500 500 0 0 0
local qdhello flood 1 0 0 0
0 0 0 0 5
local qdrouter flood 1 0 0 0
0 0 0 0 0
topo qdrouter flood 1 0 0 0
0 0 0 0 10
local qdrouter.ma multicast 1 0 0 0
0 0 0 0 0
topo qdrouter.ma multicast 1 0 0 0
0 0 0 0 3
local temp.Z5XxqC2eTxXIfxF closest 0 1 0 0
0 0 0 0 0
*qdstat -l*
Router Links
type dir conn id id peer class addr phs cap
undel unsettled deliveries admin oper
=======================================================================================================================
endpoint in 8 19 mobile cluster.queue 1 250
0 0 500 enabled up
endpoint out 8 23 mobile cluster.queue 0 250
0 0 500 enabled up
endpoint in 15 35 mobile cluster.queue 1 250
0 0 0 enabled up
endpoint out 15 39 mobile cluster.queue 0 250
0 0 0 enabled up
endpoint in 23 48 mobile $management 0 250
0 0 1 enabled up
endpoint out 23 49 local temp.kKB_zhktsaZy3zy 250
0 0 0 enabled up
--
View this message in context:
http://qpid.2158936.n2.nabble.com/FW-qpid-dispatch-No-load-balancing-if-destination-is-available-on-2-brokers-tp7644393p7644423.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
