Maybe some kind of initial delay property that should delay the lock attempt as part of the policy. This way you could set a higher delay on the slave than on the primary. The delay should then be configured from the outside eg. property file.
Somehow (my stomach I guess) I'm not quite sure of the practical use of the lock solution. Master/slave on eg. karaf or servicemix would be a cleaner cut. One would also have to consider situations when slaves has become master on one node (in case of failure on one node) and you want to bring back the master. /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-tp4984581p4988271.html Sent from the Camel - Users mailing list archive at Nabble.com.
