ActiveMQ clustered replicatedLevelDB configuration

["Craig A. Hill" <Cr...@sysatl.com>]

When I get 3 ActiveMW servers running with Zookeeper to manage them,
They form a Master with Slave A  and Slave B.   Slave B tries to connect to Master
Causing Slave A to disconnect, then Slave A does a retry connection which causes Slave B
to disconnect, they keep thrashing back-and-forth spitting out exceptions

activemq-osgi - 5.10.0 | Using the pure java LevelDB implementation.
activemq-osgi - 5.10.0 | Attaching to master: tcp://localhost:64054
activemq-osgi - 5.10.0 | Slave started
activemq-osgi - 5.10.0 | Attaching... Downloaded 0.00/0.00 kb and 1/1 files
activemq-osgi - 5.10.0 | Attached
activemq-osgi - 5.10.0 | Unexpected session error: java.io.IOException: An existing connection was forcibly closed by the remote host
activemq-osgi - 5.10.0 | Using the pure java LevelDB implementation.
activemq-osgi - 5.10.0 | Attaching to master: tcp://localhost:64054
activemq-osgi - 5.10.0 | Attaching... Downloaded 0.00/0.00 kb and 1/1 files
activemq-osgi - 5.10.0 | Attached


The Master just says this:
activemq-osgi - 5.10.0 | Slave has connected: 0538866c-63a7-459a-a9ee-c1a8c641b6ab
activemq-osgi - 5.10.0 | Slave has connected: 0538866c-63a7-459a-a9ee-c1a8c641b6ab
activemq-osgi - 5.10.0 | Slave has connected: 0538866c-63a7-459a-a9ee-c1a8c641b6ab
activemq-osgi - 5.10.0 | Slave has connected: 0538866c-63a7-459a-a9ee-c1a8c641b6ab


Must be some sort of port contention to the Master, I assume this is not the way it is supposed to work.


Craig