So I found one issue that seems to have stabilized it a bit. My ops gave me 3 boxes with only 1 Gig Ram and 1 CPU.
I increased that to 4 Gig Ram and 2 CPU's and it seems to be running better. I don't see any out of order messages so nothing to report. I performed a few reboot's to test fail over and the NMS clients seem to resume the fail-over but it seems to take a bit longer then I like. I still get this error: 2016-03-07 11:55:01,334 | WARN | Invalid log position: 195605985 | org.apache.activemq.leveldb.LevelDBClient | Thread-14 2016-03-07 11:55:01,335 | WARN | Invalid log position: 195609854 | org.apache.activemq.leveldb.LevelDBClient | Thread-14 2016-03-07 11:55:01,336 | WARN | Invalid log position: 195613723 | org.apache.activemq.leveldb.LevelDBClient | Thread-14 2016-03-07 11:55:01,336 | WARN | Invalid log position: 195617592 | org.apache.activemq.leveldb.LevelDBClient | Thread-14 2016-03-07 11:55:01,337 | WARN | Invalid log position: 195621461 | org.apache.activemq.leveldb.LevelDBClient | Thread-14 I'm not sure what that is all about. Other note: I had to remove the transacted=true as it was stopping and starting the connectors over and over. Also I'm not using connectionpooling should I be? Thanks Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Help-with-a-Failover-testing-that-shows-missing-messages-tp4707916p4708987.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
