Hi folks, I've been sidetracked for a while but have everything
up and running now. We use load balancing so the critical part
of our resulting configuration became this:
workers.properties:
worker.serverB-lb.type=lb
worker.serverB-lb.sticky_session=1
worker.serverB-lb.session_cookie=JSESSI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike,
On 4/28/12 10:52 AM, Mike Wilson wrote:
> uriworkermap.properties /* = serverA /path2/* = serverB
> /path3/* = serverB /path3/xyz/* = serverA
Like André, I'm curious about this, too. I would have expected some of
these things to interfer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Esmond,
On 4/30/12 8:06 AM, Esmond Pitt wrote:
>> I am not sure that mod_jk mappings follow the principle of
>> "longest match
> wins".
>
> They follow a logic of their own whereby wildcard matches outrank
> non-wildcard matches, so for example:
>
> I am not sure that mod_jk mappings follow the principle of "longest match
wins".
They follow a logic of their own whereby wildcard matches outrank
non-wildcard matches, so for example:
JkMount /*
JkUnmount /
doesn't operate to unmount the Tomcat root, not because it is shorter but
because it
Mike Wilson wrote:
I need to set up a configuration where a site's path space
gets distributed over two servers and I'm looking at using
mod_jk like this:
Apache httpd
mod_jk
workers.properties
workerA -> serverA
workerB -> serverB
uriworkermap.properties
On 28.04.2012 16:52, Mike Wilson wrote:
I need to set up a configuration where a site's path space
gets distributed over two servers and I'm looking at using
mod_jk like this:
Apache httpd
mod_jk
workers.properties
workerA -> serverA
workerB -> serverB
u
I need to set up a configuration where a site's path space
gets distributed over two servers and I'm looking at using
mod_jk like this:
Apache httpd
mod_jk
workers.properties
workerA -> serverA
workerB -> serverB
uriworkermap.properties
/* = server
