Hi Tim, Thank you for your assistance and your quick response.
As for the questions, let me try to explain better: 1. We have 2 ActiveMQ Services installed (A, B) on different machines (Amq1, Amq2) which are configured in ActiveMQ Failover configuration- Both relay on a single SQL database. This single database is configured in SQL Failover configuration using 2 Microsoft SQL Servers (Server1, Server2) 2. When shutting one of A or B, it fails-over *properly* to the other one. 3. However when the database fails-over- both ActiveMQ *services* A and B go down. 4. When starting again the services they connect properly. So to sum it up: The problem is that when there's SQL Failover, the ActiveMQ can't recover by itself, It won't reconnect by itself until we start manually back the Service. I can't believe that this is the normal behavior of ActiveMQ, Especially since the SQL Failover starts and ends within a very short period of 30 seconds or so. * When I say "Service" - I infer to the installed ActiveMQ Windows Service. -- View this message in context: http://activemq.2283324.n4.nabble.com/Crushing-JDBC-driver-with-Failover-Master-Slave-MS-SQL-database-tp4702654p4703584.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
