This is done through jvmRoute so you have to make sure the settings in
workers.properties would match jvmRoute on the application server side.
This route gets appended to your JSESSIONID, take a look at the cookies in
your browser...
If you want more details just set: JkLogLevelinfo
Regards,
G
Hi Gabriel,
It works fine, thanks ! :-)
I'm just curious abount one thing:
If I shutdown apache at "server1", my browser access only "server2"
and return to access "server1" if I run apache again. It's awesome,
but as I know this failover is not expected when using DNS
round-robin... :-/
Hi,
Would be more efficient to use mod_jk in load balancing and use:
worker.loadbalancer1.sticky_session=1.
If you are looking for session replication then your container should
support that.
Gabriel
Fabri
Hi all !
I have two apache 1.3.x servers with mod_jk and jboss servers in the
same machines.
This is my scenario:
server1: apache <--> mod_jk <--> jboss
server2: apache <--> mod_jk <--> jboss
I'm using a DNS round-robin with address "www.myapplication.com"
poiting to our two apache/jboss serv
