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.
