[ https://issues.apache.org/activemq/browse/AMQ-831?page=all ]
james strachan resolved AMQ-831. -------------------------------- Fix Version/s: 4.1 Resolution: Fixed For description of the feature see: http://activemq.org/site/jdbc-master-slave.html > provide a JDBC based exclusive lock so that if just using the > JDBCPersistenceAdapter (without the journal) we can have failover of brokers > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: AMQ-831 > URL: https://issues.apache.org/activemq/browse/AMQ-831 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker > Reporter: james strachan > Assigned To: james strachan > Fix For: 4.1 > > > It would be good to be able to start, say, 3 brokers all talking to the same > database such that the first one in locks a table with an exclusive lock and > stops other nodes from getting in. If that broker fails, its connection to > the database dies then another broker should be able to jump in and take over. > Basically a JDBC version of the file locking mechanism already in the journal > code such as in these examples... > http://svn.apache.org/viewvc/incubator/activemq/trunk/activeio/activeio-core/src/main/java/org/apache/activeio/journal/active/ControlFile.java?view=markup > http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/store/DefaultPersistenceAdapterFactory.java?revision=421936&view=markup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira