We are using the JDBC master slave deployment of activemq with Oracle datasource. I was trying the failover scenarios and found that if I kill the master or shutdown the master gracefully then the secondary becomes the master alright. However, if I reboot the master server, the secondary never becomes the master. Also, when the original master is booted up and tries to acquire the lock it cannot acquire the lock - so at this point both the nodes are just waiting for acquiring the lock with the following message -
Attempting to acquire the exclusive lock to become the Master broker My only option is now to either kill the blocking session in oracle or reboot the oracle server. Any help would be greatly appreciated! -- View this message in context: http://www.nabble.com/JDBC-Master-slave-does-not-work-when-the-primary-node-is-rebooted-tp21447932p21447932.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
