Yes, this will work. The only bad thing will be, that the requests
belonging to one session will be logged partially on both of the IIS
instances, so if you try to debug a problem, you always need to look at
both IIS servers.
Stickyness works like this:
- you set a unique jvmRoute in the engine element of server.xml
- Tomcat appends the jvmRoute to each sessionid it generated, with a dot
as a separator
- mod_jk load balancer looks for a session id whenever it receives a
request and strips of the routing string behind the dot
- if mod_jk finds such a routing strings, the load balancer searches for
a worker with the same name or with a route attribute with the same
value and sends it there
So mod_jk does not hold any state information about where which session
lies. Every request carries the information with it.
Regards,
Rainer
Ian Buzer wrote:
Hi,
I currently have one IIS server balancing requests to two Tomcats using JK
1.2. I am using JK to provide sticky sessions and all is working well.
I would like to be able share requests across a second IIS server, however I
am unable to create sticky sessions at the web server level so requests
could go to either web server.
My question is, if I point both IIS servers to both Tomcats, will this work
correctly? Will the sessions still get directed to the correct Tomcat, and
will the two JKs still be able to choose the best worker for new sessions?
Many thanks
Ian
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
