Hi Guillaume,
That's great. Will servicemix still prefer to do sticky routing but
then fall back to an alternate node, or will it be more arbitrary?
thanks,
jamie.
On 4/13/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> This should now be possible.
> You have to put the following line
> exchange.setProperty("org.apache.servicemix.provider.stateless",
> Boolean.TRUE);
> before sending the exchange containing the answer.
> This way, the exchanges can be received by any instance of the component.
>
> Cheers,
> Guillaume Nodet
>
>
> On 4/11/06, Jamie McCrindle <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I've been doing some testing in a cluster and it turns out (quite
> > reasonably) that an InOut exchange can't reply if it's source
> > component is not available even if there are multiple instances of
> > that component in a cluster.
> >
> > If it's a stateful process engine that sent out the InOut exchange and
> > it's clustered to multiple nodes, any one of them should be able to
> > accept the returning InOut exchange.
> >
> > Is there a way that servicemix could allow this kind of failover?
> >
> > Regards,
> > Jamie.
> >
>
