Hi, I observed that there is an issue with the JDBC master/slave configuration wherein the master broker does not release the DB lock if the master broker loses DB connectivity. Due to this the slave does not become the master and when the master is restarted, it too does not become the master.
There is an issue logged for this in jira: https://issues.apache.org/activemq/browse/AMQ-1958 I wanted to check if there are any workarounds for this issue? Can a custom database locking logic be plugged into ActiveMQ? I observed that the JDBCPersistenceAdapter bean has a databaseLocker attribute. Could this be used to plug-in a customized db locking code? -Ashish -- View this message in context: http://activemq.2283324.n4.nabble.com/JDBC-Master-Slave-Workaround-for-the-issue-due-to-which-master-broker-does-not-release-lock-tp3733813p3733813.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
