It is a junit test case. Have a look at the code to see how it sets up
brokers and
validates connection/reconnection and rebalance.
if you download the activemq trunk source[1] you can modify it at will
and run it with:
mvn clean install -Dtest=FailoverComplexClusterTest
[1] http://activemq.apac
Hi,
I am indeed using ActiveMQ 5.6 with randomize=true on my connection string.
But not sure if it's the same issue.
What exactly is that test case and how do I use it?
Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Adding-nodes-to-Cluster-without-restarting-tp4
Are you using 5.6, this looks a bit like
https://issues.apache.org/jira/browse/AMQ-3706
The test case attached to that jira may provide a good starting point
for a junit test case for your scenario, that could help reproduce
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/
Okay,
So I was able to achieve that by configuring the third broker like this:
/
duplex="true" />*
:
/
When I bring up the third broker, the clients rebalance themselves among the
several nodes.
Now, I want to update the configuration of the first two brokers. So I take
down one of them a
