Hello Wim! We are using master/slave on Karaf level. Karaf is starting the Jetty container (because we use the jetty.xml file for configuring it and do not start multiple Jetty instances for different services).
Best, Christian On Tue, May 27, 2014 at 5:09 PM, Wim Verreydt <[email protected]> wrote: > Hi Christian, > > On which level do you use master/slave? (karaf, activemq, …) > If you use master/slave on a karaf-level, your slave container should not > start until the other container quits (and not open any ports). > > What capabilities does your load balancer support for health checking? > > Just to have a quick fix for your proposal, you could expose your service > on a non-standard servicemix port so this only comes available when the > service starts. (or change your default ports for ServiceMix) > > In general for webservices I would suggest a service endpoint with > master/master setup. > > I hope this is of any help to you, > > Wim > > > On 23 May 2014, at 17:08, Christian Müller <[email protected]> > wrote: > > > Hello guys! > > > > We are using Apache ServiceMix (Fuse ESB 7.1.0) in a master/slave > > configuration. We are providing some web services in our application > (based > > on Apache Camel) by using the OSGI servlet service (central jetty.xml > > configuration). Everithing works fine so far.If the instance 1 (master) > > goes down, the instance 2 (slave) will take over. Our load balancer will > > detect this and forward the requests to instance 2 (now master). > > > > Our issue is, if we start instance 1 again (now slave), the load balancer > > detects the http port is available again (but not the service behind) and > > forward the requests to instance 1 (which cannot handle the requests > > because he is the slave). > > > > Any recommendations how we should handle this? > > We do not use any web console in ServiceMix. > > > > Thanks in advance, > > Christian > >
