You could look at route policy, and then let the "failover" routes do a thread sleep before they start, the route policy has some apis you can hook into the lifecycle of the route.
You would need to figure out somehow which route is the master and not sleep for that one. On Mon, Feb 22, 2016 at 7:50 PM, fliot <[email protected]> wrote: > My camel consumers are not geographically at the same distance from broker, > And network bandwith have some cost... > > I just reviewed the exclusive consumer documentation, it doesn't fit exactly > to my need, > I was looking for something like a balance factor, with which I could set to > define how consumer can act. > > Thanks anyway for the answer. > > Regards. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Activemq-initialDelay-tp5778033p5778075.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
