Build you own load balancing algorithm to select the "last known good" choice and then keep use that, and if that fail, then try another etc.
The Camel LB allows to plugin custom algorithms. On Sun, Nov 3, 2013 at 4:50 PM, pmp.martins <pmp.mart...@campus.fct.unl.pt> wrote: > I don't want to build a reliable messaging / clustering alternative. All I > want is to be able to stop sending messages to a certain endpoint B, and > replicate it in another machine in order to manage load or for some other > reason. I merely use the LoadBalancer component with the failover construct > because everyone keeps saying that is what I am looking for, even though it > won't work 100% as expected because Processor A will keep trying to send > information to a processor that I no longer want to, and will only send > information to the new processor as a last alternative. > > If there is an easier way to do it, I'm all ears :S > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Migrate-Apache-Camel-Endpoints-tp5741899p5742562.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
