Hi We have debated this before on this mailing list, so you would maybe be able with a bit luck to google those threads.
If you use Apache ServiceMix to host your Camel applications then it offers clustering capabilities, using its NMR, JBI or JMS transports. You can also consider embedding AMQ and use JMS. There is a clustering guide at FuseSource http://fusesource.com/products/enterprise-activemq/#documentation There is also hazelcast and other similar for in-memory grids. We recently added Camel integration for that: http://camel.apache.org/hazelcast-component.html On Mon, Apr 11, 2011 at 10:48 AM, Christoph Burmeister <[email protected]> wrote: > Hi, > > I'm pretty new to Apache Camel, and I want to figure out, if I can use > it for our application. > > Following case: two Camel-instances, running on different physical > servers. Both will receive the same messages from > 3rd-party-application (which is configured to send to the two > ip-adresses). If the first Camel is up and running the second Camel > should ignore the incoming message, otherwise the second Camel should > process it. > So far the situation. I know there is a possible solution by using a > load-balancer and then route the message via fail-over-strategy to the > instances. But in case of a broken load-balancer, I have just two > useless Camel-instances. > > My solution would be a kind of "Hello"-Message, which is sent from the > second Camel to the first Camel (with ack), to make sure, that the > first is still living. Main-target is to receive all(!) messages and > process them. > > Do you have any ideas how to realize this or do you have another > solution regarding my needs? Thanks in advance, > > best, > Christoph > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com CamelOne 2011: http://fusesource.com/camelone2011/ Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
