Hi,
I'm using the domain property in the same situation as the one
discussed in this thread. Any reason why I shouldn't use the domain
property and rely on the worker names instead?
Thanks in advance,
-- Edgar Alves
Rainer Jung wrote:
That should not work!
The correct way to configure
Edgar Alves wrote:
Hi,
I'm using the domain property in the same situation as the one
discussed in this thread. Any reason why I shouldn't use the domain
property and rely on the worker names instead?
Domain is supposed to be used with multiple workers sharing the
same jvmRoute having
Hi Mladen,
I've used the domain property because it seemed the more general
approach (i.e., supports clusters but can be used with a single worker).
What this thread got me curious about is if using the domain property in
this fashion is officially supported, or on the other hand if it can
only
OK, thanks Mladen: I have to correct myself.
1) Traditional use
Until mod_jk 1.2.6 there was no concept of domains. You had to specify the
worker name to be exactly the same as the jvmRoute to make sticky sessions
work. This way of configuring stickyness is wel known to mod_jk users.
2) I
Try adding these two lines to worker.properties:
worker.bl_worker_dev.domain=dev_alexis
worker.bl_worker_noah.domain=noah_alexis
-- Edgar Alves
Mott Leroy wrote:
Hi -
I'm unable to get mod_jk load balancing working. The usual mod_jk
setup works just fine, but using a load balancing worker
Beautiful - worked like a charm. That might take the cake as far as
longest question to quickest, shortest answer goes. ha. Thanks a bunch.
I might have to gripe about doucmentation in a second (nother thread)..
Noah
Edgar Alves wrote:
Try adding these two lines to worker.properties:
That should not work!
The correct way to configure session stickyness is to use jvmRoute (which
you already did) and then giving the workers the same names as the
jvmRoute. That is instead of bl_worker_dev use dev_alexis and instead
of bl_worker_noah use noah_alexis as the worker names.
You
Ok - noted. I changed it. It works without the domain as you noted. Thanks.
Rainer Jung wrote:
That should not work!
The correct way to configure session stickyness is to use jvmRoute (which
you already did) and then giving the workers the same names as the
jvmRoute. That is instead of
