I've just committed this fairly simple addition to allow users who are not using the high performance journal and are just using pure JDBC for persistence to use a JDBC specific version of master slave which allows many slaves to be run with auto-failover http://activemq.org/site/jdbc-master-slave.html
This works in a similar way to the shared file system master slave approach, using an exclusive lock to implement the master but relying on an exclusive database lock rather than a file lock. http://activemq.org/site/shared-file-system-master-slave.html -- James ------- http://radio.weblogs.com/0112098/
