Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 angeshwar@gmail.com does not designate 216.139.250.139 as permitted sender)
Date: Tue, 10 Dec 2013 04:34:29 -0800 (PST)
From: deepak_a <angeshwar@gmail.com>
To: users@activemq.apache.org
Message-ID: <1386678869083-4675328.post@n4.nabble.com>
Subject: Regarding Pluggable+storage+lockers
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.