I don't think the scenario you describe is doable. Camel does not offer any transparent clustering, so if you create a route with multiple steps, all the steps should be included in a single transaction, so that the whole route will be rolled back if something bad happens. If the route begins with a JMS endpoint, you could easily set up persistence, transaction and all the QoS needed at this point.
On Tue, Apr 8, 2008 at 9:37 PM, chintaka <[EMAIL PROTECTED]> wrote: > > I am curious to know how camel will behave in the following setting : > > 1) You have multiple clusters (A and B) > 2) Each cluster has a copy of camel route for redundancy and load > balancing. > 3) Router in cluster A is executing a routing slip type process(a process > with multiple steps), at this point if the cluster A goes down router in > cluster B should pickup the routing ? > 4) If so what happens to state of the message that router in cluster A > started executing ? > > Thanks, > > Chintaka > -- > View this message in context: > http://www.nabble.com/Camel-in-a-Clustered-Environment-tp16571337s22882p16571337.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
