This is normal and expected behavior for ActiveMQ with KahaDB as well. I've never used LevelDB, so I can't speak to its behavior, though I have no reason to believe it would behave differently than the other two.
ActiveMQ can't work without a backing store if you've configured it to require one. What would it do while it was up without the ability to accept messages? Should it keep accepting connections when it can't accept or deliver messages on them, depriving clients of the ability to fail over to a broker that was actually alive? This is how ActiveMQ works, and I'm not aware of a way to configure it to behave otherwise (nor do I think such an ability should exist). If you need a workaround that allows you to handle periods of time (short or long) when your database is unavailable, you could script a process to watch for the ActiveMQ process to not be running and restart it... It wouldn't be unreasonable to allow the ability to configure how long to retry the connection before giving up on it and halting the server, so you could submit an enhancement request for that if you wanted. But for right now, monitoring and restarting the process seems like your best bet. Also, you haven't answered my question: can ActiveMQ connect successfully after the database failover? Is the problem simply that ActiveMQ is re-testing the connection sooner than the failover process makes it available again? Or is the problem that your broker can't connect to a failed-over database no matter how long you wait? Tim On Sun, Nov 1, 2015 at 1:26 AM, Abrasha70 <yair...@gmail.com> wrote: > Of course it fails, but it should not put the service down. > The service should keep running until it can reconnect. > > I believe this is not a normal behavior of ActiveMQ, > and if it is, how can I config it otherwise? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Crushing-JDBC-driver-with-Failover-Master-Slave-MS-SQL-database-tp4702654p4703577.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
