-
1. Re: stick session configuration failing
rgore Sep 4, 2003 8:04 AM (in response to rgore)I am not exactly sure why any of this works like this. But this is what I have learned so far.
I have included code from two workers2.properties files. One works with sticky sessions, the other does not. Using the second one my application is now working with sticky sessions!
The following workers2.properties did not behave properly with sticky sessions:
[logger]
level=DEBUG
[config:]
file=${serverRoot}/conf/workers2.properties
debug=0
debugEnv=0
[uriMap:]
info=Maps the requests. Options: debug
debug=0
# Define the communication channel
[channel.socket:www.testmachine1.tv:8009]
info=Ajp13 forwarding over socket
tomcatId=www.testmachine1.tv:8009
lb_factor=1
group=lb
# Define the communication channel
[channel.socket:www.testmachine1.tv:8009]
info=Ajp13 forwarding over socket
tomcatId=www.testmachine1.tv:8009
lb_factor=1
group=lb
# Map the Tomcat examples webapp to the web server uri space
[uri:/NetMovies/*]
info=Map the whole webapp
[shm:]
info=Scoreboard. Required for reconfiguration and status with multiprocess servers
file=${serverRoot}/logs/jk2.shm
size=1000000
debug=1
disabled=0
This is my workers2.properties file that does work correctly with sticky sessions:
[shm:]
file=${serverRoot}/logs/jk2.shm
size=1048576
[lb:lb_01]
info=Default Load Balancer.
debug=10
# Define the worker
[channel.socket:www.testmachine1.tv:8009]
info=Ajp13 forwarding over socket
tomcatId=worker1:8009
lb_factor=100
group=lb_01
# Define the worker
[channel.socket:www.testmachine2.tv:8009]
info=Ajp13 forwarding over socket
tomcatId=worker2:8009
lb_factor=100
group=lb_01
# map /NetMovies
[uri:/NetMovies/*]
group=lb_01
debug=10
[logger]
level=DEBUG
[config:]
file=${serverRoot}/conf/workers2.properties
debug=10
debugEnv=0 -
2. Re: stick session configuration failing
rgore Sep 4, 2003 9:42 PM (in response to rgore)After many hours of toil, still seeing strange behavior with the sessions, I went back to Apache 1.3.28 and mod_jk and had the load balancing working in about an hour. I'm sure this must work on apache2/mod_jk2/jboss322, but I was never able to get it to work properly. It works with apache1/mod_jk/jboss3.0.4 wonderfully.