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.
