tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Hanik - Dev" <devli...@hanik.com>
Subject Re: [VOTE] Proposed API change to the Manager interface
Date Tue, 08 Feb 2005 17:25:39 GMT
its not at all that complicated.
This is how a big5 load balancer does it.

A) it sets a cookie, and based on the cookie it load balances.
B) if a cookie is not supported, it does a calculation based on the IP address, and stays
sticky that way.

No need to exchange any info in this scenario and very straight forward, and never goes wrong.
The only time it goes wrong is for
AOL users who can change gateway between HTTP and HTTPS

Filip

----- Original Message -----
From: "Rainer Jung" <tomcat-dev@kippdata.de>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Tuesday, February 08, 2005 10:39 AM
Subject: Re: [VOTE] Proposed API change to the Manager interface


I'm afraid that change will have negative implications: The jvmRoute is
used to enable routing decisions by balancing components. All these
components usually support routing either COOKIE-based or URI-based.

In the URI-based case it is more or less the only clean way to include
the jvmRoute in the jsessionid, since the jsessionid is standardized, so
all common balancing products know how to handle it.

But then it is pretty common to assume the jsessionid and the cookie to
have the same value. They are sort of two different ways to transport
the same session information. So most balancer providers implement the
routing decision features the same way, independant of the source of the
session string.

Splitting the jvmRoute from the session id in the cookie case will most
likely make the situation for all implementers of balancers more complex
and instable (e.g.: mod_jk).

Of course we would all profit, if some JSR would standardize the way,
distributed applications exchange routing information with the
clients/balancers. As long as that's not the case it is very likely,
that jvmRoute as a suffix of the session id has much better support from
balancer providers.

Rainer

Filip Hanik - Dev wrote:

> Remy Wrote:
>
>>BTW, wouldn't it be better to set the route as a separate cookie, which
>>would be a lot cleaner ? Was this ever considered ?
>
>
> That would have been the obvious solution, the jvmRoute must have come from a dark basement
somewhere :)
>
> Whatever the change you decide on, I'll be happy to implement it and test it for the
cluster stuff
>
> Filip
>
> ----- Original Message -----
> From: "Remy Maucherat" <remm@apache.org>
> To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
> Sent: Monday, February 07, 2005 11:34 AM
> Subject: Re: [VOTE] Proposed API change to the Manager interface
>
>
>
>>@@ -744,15 +747,17 @@
>>         session.setValid(true);
>>         session.setCreationTime(System.currentTimeMillis());
>>         session.setMaxInactiveInterval(this.maxInactiveInterval);
>>-        String sessionId = generateSessionId();
>>+        if (sessionId == null) {
>>+            sessionId = generateSessionId();
>>+        }
>
>
> I just noticed my patch needs something for jvmRoute handling
> (basically, the session id which is recieved must be edited for the
> right route). I'll fix that.
>
> BTW, wouldn't it be better to set the route as a separate cookie, which
> would be a lot cleaner ? Was this ever considered ?
>
> Rémy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message