I ran into similar requirements and needed route level locking to single-thread execution across routes that act on the same data. These could be identical routes deployed in a cluster or different routes altogether that "act" on the same data.
I was planning on adding this to Hazelcast (see CAMEL-4397), but am still investigating the options (see http://camel.465427.n5.nabble.com/discuss-implementing-Locks-in-Camel-td4775904.html this discussion ). My approach was geared towards blocking threads rather than not starting routes altogether, but I think the motivation is similar. Either way, Hazelcast seems to be applicable to both scenarios... Hopefully we can implement some form of this as I think the use case is becoming more common as more people are using clustered deployments of Camel these days... ----- Ben O'Day IT Consultant -http://consulting-notes.com -- View this message in context: http://camel.465427.n5.nabble.com/Single-route-inside-cluster-tp4806241p4807354.html Sent from the Camel - Users mailing list archive at Nabble.com.
