The system i'm currently testing with is only a little test system,
it is not inteded to go productive in that configuration ;-)
But thanks for the tip you anyway. The jk.log has no error messages,
and here is the log grepped for "found best worker":
[Tue Oct 25 15:52:23 2005] [28304:49172] [debug
Hi,
here the requested files:
workers properties:
---
#
# wokers.properties - configuration for mod_jk
#
# configure path separator
ps=/
# list of workers by name
worker.list=loadbalancer
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=debi1, debi2
worker.load
Hi,
thanks for the quick response, jvmRoute is configured on both instances.
We do not use the standard tomcat url rewriting (which is
http://...;jsessionid=...?x=y),
we use simply a standard http paramter and do our own url rewriting.
Regards,
Tom
> Did you set the jvmRoute="your worker name"
Hi list,
I'm using apache 2.0.54 + mod_jk 1.2.14 on a debian 3.1 server.
I have 2 tomcat workers running on different machines.
Although I configured the load balancing worker with sticky_session=1, all
requests get spread over the tomcat workers in round robin.
My question is, how does mod_jk
