Thank you Rainer,
Now Apache is working with disable mode. Maybe later it changed again.

:)


2011/6/12 Rainer Jung <rainer.j...@kippdata.de>

> On 12.06.2011 09:30, Manuel Fernández Panzuela wrote:
> > Is possible to combine both attributes distance - activation ?
> > Distance looks like a very interesting attribute.
>
> Yes, of course you can combine. As long as you don't cnfuse yourself
> because it gets too complicated.
>
> Distace (e.g. 0 and 1) will lead to normally everything being sent to
> the "close" node, but when you switch its activation from active to
> disabled, new sessions will be created on the node with higher distance.
> Switching to "stopped" will result in every request being handled by the
> node with higher distance.
>
> Regards,
>
> Rainer
>
> > 2011/6/11 Rainer Jung <rainer.j...@kippdata.de>
> >
> >> On 08.06.2011 12:12, Felix Schumacher wrote:
> >>> Am Mittwoch, den 08.06.2011, 09:47 +0200 schrieb Manuel Fernández
> >>> Panzuela:
> >>>> Yes Felix, you are right i am working with 2 instances.
> >>>> I want primary node receives all requests and on failure send requests
> >> to
> >>>> the secondary node.
> >>>> Is it possible with your recomendation ?
> >>> You may also want to read
> >>>
> http://tomcat.apache.org/connectors-doc/generic_howto/loadbalancers.html
> >>> if http://tomcat.apache.org/connectors-doc/reference/workers.html was
> >>> not helpful.
> >>>
> >>>>
> >>>> worker.43m2g1.activation=d
> >>>> degraded ??? is a condition ? then all requests will be redirected to
> >> 43m2g1
> >>> disabled
> >>
> >> The attribute "distance" provides an alternative approach.
> >>
> >> Regards,
> >>
> >> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Reply via email to