Pluggable storage lockers allows you to change the locking strategy of ActiveMQ storage and master/slave elections. It doesn't have anything to do with Camel in your scenario per-se.
To see how ActiveMQ does it for SQL server, take a look here: https://github.com/apache/activemq/blob/trunk/activemq-jdbc-store/src/main/java/org/apache/activemq/store/jdbc/adapter/TransactDatabaseLocker.java#L46 On Tue, Dec 10, 2013 at 4:34 AM, deepak_a <angesh...@gmail.com> wrote: > All, > > I am running ActiveMQ (5.6.0) integrated in JBoss. I am also using Apache > Camel. > ActiveMQ runs in a master/slave fashion. > > To ensure failover of Apache Camel routes, I have implemented strategy as > shown below > http://www.liquid-reality.de/display/liquid/2011/11/11/Hot+Standby+failover+for+Apache+Camel+routes > > - This ensures that when the master acquires a lock on the database, the > slave (Camel) waits until master release lock (i.e. Master fails) - then > slave takes over > > Does the Pluggable+storage+lockers described below - help me achieve the > same? > https://cwiki.apache.org/confluence/display/ACTIVEMQ/Pluggable+storage+lockers > I presume not? can some one clarify > > > Note: the strategy I am following works perfect! However the query I use > select ...for update works fine (in holding lock in Oracle database but > fails with SQL Server - since it does not support select ... for update) > > regards, > D > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Regarding-Pluggable-storage-lockers-tp4675328.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta
