I have a JDBC master slave configuration for ActiveMQ using oracle persistence. When I restart my database server while primary and secondary are both running, SQL exception occurs which is fine, but when the db comes back up, both the activemq servers become available.
The only solution is to restart both the brokers which is kind of ugly -- View this message in context: http://www.nabble.com/Active-MQ-master-slave-using-JDBC---Database-restart-tp18937851p18937851.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
