Hi Mike, but this only makes sense when you use multiple instances on different machines. Doing Failover on the same machine I would rather not recommend.
Regards, Achim 2011/3/29 Michael Dewitte <michael.dewi...@gmail.com>: > Hi, > > nice thread, thanks for the sharing... to me, multiple instances makes sense > for fail-over. Just configure it through the ActiveMQ... > > Mike > > > 2011/3/29 Achim Nierbeck <bcanh...@googlemail.com> > >> Hi Gonzalo, >> >> Makes sense, besides one point, why do you expect you need multiple >> Karaf instances? >> Regarding Camel or Spring there is no need to deploy those in extra >> Servers, because you only got >> one CamelContext/SpringContext per bundle. Therefore I'm sure you can >> use one Karaf instance with all your routes. ActiveMQ can be deployed >> on top of Karaf too, since it is the basis for ServiceMix :) >> >> One reminder though, if you need to communicate effectively between >> different Camel routes in different bundles you should think about >> NMR, which runs best with ServiceMix :) >> >> >> Regards, Achim >> >> 2011/3/29 gonzalo diethelm <gdieth...@dcv.cl>: >> >> Hi, >> > >> > Hi Achim, thanks for answering. >> > >> >> just my 0.02$ on a container/runtime. >> >> My best experience as runtime for Camel is to use Karaf. >> >> If you need more out of the box components like ActiveMQ and so forth >> >> you might also consider to use Servicemix. >> > >> > OK, my incipient plan so far is to use Karaf to host each of my services >> as a separate bundle, and maybe have several Karaf instances running on a >> single machine. Each bundle (service) will use Spring for its configuration >> and wiring, including bootstrapping Camel. I expect to be able, as well, to >> configure ActiveMQ in this setup directly from Spring, and hopefully avoid >> (for now) ServiceMix, since it seems "pure" Camel will cover all my needs. >> Does this make sense to you? >> > >> > -- >> > Gonzalo Diethelm >> > >> > >> >
