Hi,

I was having a problems with my sessions not sticking to the correct web
server in a load balanced cluster. If I set tomcatId/jvmRoute to a
value that does not contain a period, the problem goes away. I'm using
Apache 2.0.47 with JK 2.0.2.

Has anyone else seend this? Is this a known bug?

Thanks,

Jonathan

---- Example error configuration ----

# This configuration appears to fail because the jvmRoute becomes
# server.mydomain.com:8009 (contains . characters).

[shm:]
file=${serverRoot}/logs/jk2.shm
size=1048576

[lb:load_balancer]

[channel.socket:server.mydomain.com:8009]
port=8009
host=server.mydomain.com
group=load_balancer
lb_factor=1

[channel.socket:server.mydomain.com:8019]
port=8019
host=server.mydomain.com
group=load_balancer
lb_factor=1

[uri:/test/*]
group=lb:load_balancer

---- Example working configuration (using localhost) ----

# This configuration works because it constructs a jvmRoute that
# looks like localhost:8009 (no periods).

[shm:]
file=${serverRoot}/logs/jk2.shm
size=1048576

[lb:load_balancer]

[channel.socket:localhost:8009]
port=8009
host=localhost
group=load_balancer
lb_factor=1

[channel.socket:localhost:8019]
port=8019
host=localhost
group=load_balancer
lb_factor=1

[uri:/test/*]
group=lb:load_balancer

---- Example working configuration (using tomcatId) ----

# This configuration works because the tomcatId sets the jvmRoute
# to server1 (no periods).

[shm:]
file=${serverRoot}/logs/jk2.shm
size=1048576

[lb:load_balancer]

[channel.socket:server.mydomain.com:8009]
port=8009
host=server.mydomain.com
group=load_balancer
lb_factor=1
tomcatId=server1

[channel.socket:server.mydomain.com:8019]
port=8019
host=server.mydomain.com
group=load_balancer
lb_factor=1
tomcatId=server2

[uri:/test/*]
group=lb:load_balancer

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)