I have a 3 node cluster on Redhat servers running ActiveMQ version 5.13.2 and Zookeeper 3.4.8
The system runs without error for days then when I fail it over it will sometimes will not recover see log segment below. The strange thing is I’m getting a Connection refused even from the master connecting to itself. Does anyone have any idea what might cause this? Server1 ActiveMQ.log 2016-03-15 11:57:27,756 | WARN | Store update waiting on 1 replica(s) to catch up to log position 1268728231. | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | ActiveMQ BrokerService[localhost] Task-24 2016-03-15 11:57:28,757 | WARN | Store update waiting on 1 replica(s) to catch up to log position 1268728231. | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | ActiveMQ BrokerService[localhost] Task-24 2016-03-15 11:57:29,758 | WARN | Store update waiting on 1 replica(s) to catch up to log position 1268728231. | org.apache.activemq.leveldb.replicated.MasterLevelDBStore | ActiveMQ BrokerService[localhost] Task-24 Server2 ActiveMQ.log 2016-03-15 11:58:27,575 | INFO | Using the pure java LevelDB implementation. | org.apache.activemq.leveldb.LevelDBClient | hawtdispatch-DEFAULT-1 2016-03-15 11:58:27,575 | INFO | Attaching to master: tcp://Server2.corp.local:61619 | org.apache.activemq.leveldb.replicated.SlaveLevelDBStore | hawtdispatch-DEFAULT-1 2016-03-15 11:58:27,577 | WARN | Unexpected session error: java.net.ConnectException: Connection refused | org.apache.activemq.leveldb.replicated.SlaveLevelDBStore | hawtdispatch-DEFAULT-1 Server3 ActiveMQ.log 2016-03-15 11:58:27,484 | INFO | Using the pure java LevelDB implementation. | org.apache.activemq.leveldb.LevelDBClient | hawtdispatch-DEFAULT-1 2016-03-15 11:58:27,485 | INFO | Attaching to master: tcp://Server2.corp.local:61619 | org.apache.activemq.leveldb.replicated.SlaveLevelDBStore | hawtdispatch-DEFAULT-1 2016-03-15 11:58:27,487 | WARN | Unexpected session error: java.net.ConnectException: Connection refused | org.apache.activemq.leveldb.replicated.SlaveLevelDBStore | hawtdispatch-DEFAULT-1 Thanks Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Leveldb-not-recovering-from-failover-tp4709307.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
