Should that not be :
jvmRoute=balancer
C.
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 14 June 2007 20:45
To: Tomcat Users List
Subject: Re: sticky sessions not sticking
change your JVM route to
jvmRoute=worker1, as I believe the jvmRoute value has
Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 14 June 2007 20:45
To: Tomcat Users List
Subject: Re: sticky sessions not sticking
change your JVM route to
jvmRoute=worker1, as I believe the jvmRoute value has to match the
name of the worker.
Filip
Eddie Yee wrote:
Hi
Rainer Jung wrote:
No, Filip is right:
1) Each Tomcat needs to have a unique jvmRoute
One side note:
jvmRoute does not need to reflect the worker name
in domain clustering model.
jvmRoute can be group1 on multiple nodes.
and workers can be:
worker.node1.xxx
worker.node1.route=group1
...
Yes, but if you use it on multiple Tomcats (as a group), it will break
stickyness.
Of course, users can use the route attribute completely instead of the
names, but most users seem to be confused by this. I tried to clarify
the docs a couple of days ago, so with 1.2.24 the frequency of this
Hi,
I am not sure if this is a bug, but it appears that my sticky sessions
configuration don't want to stick. I am running two servers with tomcat
5.5.20 (configured as single servers ie. no session replication) with
standard ajp13 connector (8009) and one web server running iPlanet 6 with
change your JVM route to
jvmRoute=worker1, as I believe the jvmRoute value has to match the
name of the worker.
Filip
Eddie Yee wrote:
Hi,
I am not sure if this is a bug, but it appears that my sticky sessions
configuration don't want to stick. I am running two servers with
tomcat
Hi Filip.
It looks like that solved the problem! Thanks for your help!
Eddie
From: Filip Hanik - Dev Lists [EMAIL PROTECTED]
Reply-To: Tomcat Users List users@tomcat.apache.org
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: sticky sessions not sticking
Date: Thu, 14 Jun 2007 21
