Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of nicolas.sarazin.pro@gmail.com
 designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAD5kzAZieNX_yyWUinThNEpFbGM0ubZTzh07RoYjfJL7P6n_dg@mail.gmail.com>
References: 
 <CAD5kzAZieNX_yyWUinThNEpFbGM0ubZTzh07RoYjfJL7P6n_dg@mail.gmail.com>
Date: Fri, 21 Sep 2012 06:58:41 +0200
Message-ID: 
 <CANbuqw7T+WRkueOozMnkpfA9PJqOsEA=1oD+jmL-ksdJbV9A-A@mail.gmail.com>
Subject: Re: Sticky sessions not working
From: Nicolas Sarazin <nicolas.sarazin.pro@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=f46d04071173fd191304ca2f17ec

--f46d04071173fd191304ca2f17ec
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,

Add :

worker.node1.route=3Dnode1

And :

worker.node2.route=3Dnode2

To use sticky session. These directives attach name route at the end of
JSESSIONID.

Best regards,

Nicolas SARAZIN

Le vendredi 21 septembre 2012, Lou Henry a =E9crit :

> I'm running Apache Tomcat 7.0.14 and Apache 2.2.21 (mod_jk1.2.37).  I
> am trying to load balance two Tomcat Servers and sticky sessions are
> not working.  I am running
> a two-factor authentication package and it looks like my LB
> configuration is directing the user to one Tomcat for part of the
> transaction and to the other Tomcat
> server for the other part. When I bring down one of the Tomcat
> servers, everything works fine; but with both Tomcat servers up, I get
> 500 errors.  So, I am trying
> to stick the webserver session to one particular Tomcat server.
> Listed below is my configuration.  Also, I tried without the domain
> directive also.  I am not quite
> sure if that's a random name or should it be something specific.
>
> Can someone please assist?  Thank you...
>
> *workers.properties*
>
> worker.list=3Dloadbalancer,status
>
>
>
> # Define Node1
>
> # modify the host as your host IP or DNS name.
>
> worker.node1.domain=3Djvm1
>
> worker.node1.port=3Dxxxx
>
> worker.node1.host=3Dt*****20.xxxxx.xxxx
>
> worker.node1.type=3Dajp13
>
> worker.node1.lbfactor=3D1
>
> worker.node1.ping_mode=3DA
>
>
>
> # Define Node2
>
> # modify the host as your host IP or DNS name.
>
> worker.node2.domain=3Djvm2
>
> worker.node2.port=3Dxxxx
>
> worker.node2.host=3Dt*****21.xxxxx.xxxx
>
> worker.node2.type=3Dajp13
>
> worker.node2.lbfactor=3D1
>
> worker.node2.ping_mode=3DA
>
>
>
> # Load-balancing behaviour
>
> worker.loadbalancer.type=3Dlb
>
> worker.loadbalancer.balance_workers=3Dnode1,node2
>
> worker.loadbalancer.sticky_session=3DTrue
>
>
>
> # Status worker for managing load balancer
>
> worker.status.type=3Dstatus
>
>
>
> # Added per Anakam direction 113010
>
> worker.node1.socket_keepalive=3DTrue
>
> worker.node1.socket_timeout=3D300
>
>
>
> # Added per Anakam direction 113010
>
> worker.node2.socket_keepalive=3DTrue
>
> worker.node2.socket_keepalive=3D300
>
>
> *server.xml on Tomcat Node 1*
>
> <Engine name=3D"Catalina" defaultHost=3D"localhost" jvmRoute=3D"node1">
>
> *server.xml on Tomcat Node 2*
>
> <Engine name=3D"Catalina" defaultHost=3D"localhost" jvmRoute=3D"node2">
>

--f46d04071173fd191304ca2f17ec--