? Please let me know.
Thanks,
Bodhayan.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-Re-balance-Question-tp3325301p3434610.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ode. Not sure which module triggers the
re-balance.
Thanks, again
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-Re-balance-Question-tp3325301p3341667.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
oker 1:
Broker 2:
Will take a look with the code. Not sure which module triggers the re-balance.
Thanks, again
From: Gary Tully
To: users@activemq.apache.org
Sent: Mon, February 28, 2011 7:28:49 AM
Subject: Re: Connection Re-balance Question
Ju
Just had a peek at the code[1], you need to add
updateClusterClientsOnRemove="true" to your transport connector.
It looks like the cluster info is not aware of the broker failure
(node removal) and as a result does not update then it joins again.
org.apache.activemq.broker.region.RegionBroker#rem
try attachment again
From: Joe Smith
To: users@activemq.apache.org
Sent: Fri, February 25, 2011 5:22:04 PM
Subject: Re: Connection Re-balance Question
Attachment.
From: Joe Smith
To: users@activemq.apache.org
Sent
Attachment.
From: Joe Smith
To: users@activemq.apache.org
Sent: Fri, February 25, 2011 5:14:51 PM
Subject: Connection Re-balance Question
Hi,
I'm using the 5.4.x transport's updateClusterClients="true"
rebalanceClusterClients="tr
Hi,
I'm using the 5.4.x transport's updateClusterClients="true"
rebalanceClusterClients="true" options.
It works fine as a broker is added to the cluster - the existing connections
are
rebalanced.
When a broker that's already in the cluster when down, the connections failed
over succes
