Hi Preben,
the only problem we will have is that my current solution always stops
itself before it tries to reacquire the lock. When using suspend /
resume on a camel route this is very light weight.
When I would try to stop and start bundles or wars this would not be a
good behaviour.
Another solution would be to use the vm transport to send the start /
stop commands to the routes. So I could have one bunlde / war that does
the locking and sends the command to all others. These could then
respond by doing the same as now (resume/suspend the routes).
Karaf has cellar. This is a cluster for configuration and deployment. So
the only thing it does is to send configuration changes and feature
changes to all nodes of a group. It does not do any HA right now.
Does Fabric support Active / Passive clusters? I thought it would be
more similar to cellar.
Christian
Am 14.11.2011 08:05, schrieb Preben.Asmussen:
Hi Christian
Year you right a delay might be to simple. The solution you mention with a
heartbeat can get quite advanced, but is more flexible I think.
Locking on infrastructure level eg. Karaf seems to me to be the right way to
go. You don't want do this for every integration, but want a flexible way to
configure this at deployment time, or even balance this at runtime (eg.
using karaf commands or jmx) if possible.
I'm not an Karaf expert - has Karaf a concept of groups ? if so can they be
used ?
and hasn't Karaf already some kind of cluster (master/slave) build in ?
Anyway Fusesource is building Fuse Fabric (open source), maybe take a peek
into that to see if there are similarities that could be used.
See you, and thanks for your good work.
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-make-your-camel-routes-highly-available-when-only-one-may-be-active-at-a-time-tp4984581p4989948.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com