Hi, If you use a JMS as your common "communication backbone" I'd say use two independent instances, just make sure if one of them dies during the consumption of a JMS message that this message doesn't get lost.
regards, Achim 2013/6/3 jimposervicemix <[email protected]> > cross-posted at > http://stackoverflow.com/questions/16896074/how-do-i-cluster-servicemix > > I am looking for some initial pointers on how to cluster a ServiceMix > solution. Basically what I need is: > > - having 2 (or more) ServiceMix instances serving my routing needs and > sharing the load > - if one instance fails, other(s) continue to serve > - if the failed one is brought back to life, it joins the party > > Searching for information confuses me since > > - some references (eg. > > http://trenaman.blogspot.fi/2010/04/four-things-you-need-to-know-about-new.html > ) > talk about "JBI cluster engine". I don't want to use JBI. Support for it is > deprecated. Is there a separate "Non-JBI cluster engine" or what is going > on...? > - I see a lot of mentions about "DOSGi". Do I need to worry my simple head > with all that if I want to achieve clustered ServiceMix? > > My solution will probably have a few bundles that communicate with each > other using JMS queues. Should I in that case just have 2 independent > ServiceMix instances (who do not know of each other). Wouldn't that be the > simplest option? I see some support for a failover configuration > (http://servicemix.apache.org/docs/4.5.x/users-guide/failover.html) but > what > benefits would that really give (am I missing something)? Also this > failover > configuration does not help with load balancing since just one instance is > serving requests. > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/How-do-I-cluster-ServiceMix-tp5716938.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
