> Does that answer your question?
Oh! I think it does. I was assuming that isapi_redirect maintained an
internal map of sessions and tomcat nodes, but if the jvmRoute is in
the session id, then it shouldn't matter which IIS/isapi is serving
the request, it will still go to the correct instance of
Dmitry Beransky wrote:
Hi Rainer,
It's the item #3 on your Simple Setup list that I'm basically asking
about (I already have #1 set up and working, and parts of #2).
Here's where my problem with #3 lies:
Let's say we have two load-balanced (clustered) web/IIS servers: W1
and W2, each configure
Hi Rainer,
It's the item #3 on your Simple Setup list that I'm basically asking
about (I already have #1 set up and working, and parts of #2).
Here's where my problem with #3 lies:
Let's say we have two load-balanced (clustered) web/IIS servers: W1
and W2, each configured with sticky forwarding
Dmitry Beransky wrote:
Hi,
Is it possible to implement the following setup with JK/isapi_redirect?
1. Two clustered IIS instances
2. Two load-balanced Tomcat instances
3. Each IIS uses JK to forward requests to two load-balanced Tomcat instances
I know how to do each individual item in i
Hi,
Is it possible to implement the following setup with JK/isapi_redirect?
1. Two clustered IIS instances
2. Two load-balanced Tomcat instances
3. Each IIS uses JK to forward requests to two load-balanced Tomcat instances
I know how to do each individual item in isolation, but I can't
fig
