You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by James Strachan <ja...@gmail.com> on 2006/07/21 16:24:35 UTC

JDBC based Master Slave

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/

Re: JDBC based Master Slave

Posted by Jason Dillon <ja...@planet57.com>.
Nice.

:-)

--jason


On Jul 21, 2006, at 7:24 AM, James Strachan wrote:

> 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/


Re: JDBC based Master Slave

Posted by James Strachan <ja...@gmail.com>.
On 7/22/06, Dain Sundstrom <da...@iq80.com> wrote:
> If you are using the Geronimo transaction manager, you may want to
> use the
> org.apache.geronimo.connector.outbound.transactionlog.JDBCLog, which
> stores the tx log in the database.  This will allow you to support
> full XA with a single non-xa jdbc connection.

Thanks, I'll bear than in mind. (We should maybe intergrate this into
Jencks as an option).

Though in this case, we don't need XA as the JDBC Master Slave is
purely used for the Broker's persistence engine and to provide high
availability and failover of brokers running against the same
database.

-- 

James
-------
http://radio.weblogs.com/0112098/

Re: JDBC based Master Slave

Posted by Dain Sundstrom <da...@iq80.com>.
If you are using the Geronimo transaction manager, you may want to  
use the  
org.apache.geronimo.connector.outbound.transactionlog.JDBCLog, which  
stores the tx log in the database.  This will allow you to support  
full XA with a single non-xa jdbc connection.

-dain

On Jul 21, 2006, at 7:24 AM, James Strachan wrote:

> 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/