You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Gomez Henri <hg...@slib.fr> on 2001/10/11 23:54:06 UTC

Re: DO NOT REPLY [Bug 4096] - Ajp13 connector does not handle stick y sessions

> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4096
> 
> Ajp13 connector does not handle sticky sessions
> 
> remm@apache.org changed:
> 
>            What    |Removed                     |Added
> ------------------------------------------------------------------------
> ----
>              Status|NEW                         |RESOLVED
>          Resolution|                            |LATER
> 
> 
> 
> ------- Additional Comments From remm@apache.org  2001-10-11 09:11
> -------
> As per Henri's comments, this will be addressed in the future.
> 

After digging into TC 3.3 and 4.0 code, it seems the jvmroute will
need to be added to TC 4.0 core (SessionId and Request).
jvmroute is used to generate the sessionid and will be returned
part of sessionid in answer.

Craig, Remy ?

BTW, it will be a needed features for warp in the future and
in the meantimes Tomcat 4.0 could be used in load-balancing
mod_jk config using 'Session Affinity'


-
Henri Gomez                 ___[_]____
EMAIL : hgomez@slib.fr        (. .)                     
PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 

Re: DO NOT REPLY [Bug 4096] - Ajp13 connector does not handle stick y sessions

Posted by "Craig R. McClanahan" <cr...@apache.org>.

On Thu, 11 Oct 2001, Remy Maucherat wrote:

> Date: Thu, 11 Oct 2001 15:16:14 -0700
> From: Remy Maucherat <rm...@home.com>
> Reply-To: tomcat-dev@jakarta.apache.org
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: DO NOT REPLY [Bug 4096]  -  Ajp13 connector does not handle
>     stick y sessions
>
> > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4096
> > >
> > > Ajp13 connector does not handle sticky sessions
> > >
> > > remm@apache.org changed:
> > >
> > >            What    |Removed                     |Added
> > > ------------------------------------------------------------------------
> > > ----
> > >              Status|NEW                         |RESOLVED
> > >          Resolution|                            |LATER
> > >
> > >
> > >
> > > ------- Additional Comments From remm@apache.org  2001-10-11 09:11
> > > -------
> > > As per Henri's comments, this will be addressed in the future.
> > >
> >
> > After digging into TC 3.3 and 4.0 code, it seems the jvmroute will
> > need to be added to TC 4.0 core (SessionId and Request).
> > jvmroute is used to generate the sessionid and will be returned
> > part of sessionid in answer.
> >
> > Craig, Remy ?
> >
> > BTW, it will be a needed features for warp in the future and
> > in the meantimes Tomcat 4.0 could be used in load-balancing
> > mod_jk config using 'Session Affinity'
>
> I think you can use the notes to store that. Would it be enough ?

Notes seem like a reasonable place to store the value, but we need to add
the code to parse the suffix off the session id (in the connector) and add
the suffix to the session id cookie or encoded url (in the response).

It makes sense to do this on the HEAD branch now, so we can confirm that
it works correctly.  Then, maybe if/when 4.0.2 comes around we can
back-port it?

> In the future, Coyote has notes too (well, it inherited them from TC 3 ;-)).
>
> Remy
>
>
Craig



Re: DO NOT REPLY [Bug 4096] - Ajp13 connector does not handle stick y sessions

Posted by Remy Maucherat <rm...@home.com>.
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4096
> >
> > Ajp13 connector does not handle sticky sessions
> >
> > remm@apache.org changed:
> >
> >            What    |Removed                     |Added
> > ------------------------------------------------------------------------
> > ----
> >              Status|NEW                         |RESOLVED
> >          Resolution|                            |LATER
> >
> >
> >
> > ------- Additional Comments From remm@apache.org  2001-10-11 09:11
> > -------
> > As per Henri's comments, this will be addressed in the future.
> >
>
> After digging into TC 3.3 and 4.0 code, it seems the jvmroute will
> need to be added to TC 4.0 core (SessionId and Request).
> jvmroute is used to generate the sessionid and will be returned
> part of sessionid in answer.
>
> Craig, Remy ?
>
> BTW, it will be a needed features for warp in the future and
> in the meantimes Tomcat 4.0 could be used in load-balancing
> mod_jk config using 'Session Affinity'

I think you can use the notes to store that. Would it be enough ?
In the future, Coyote has notes too (well, it inherited them from TC 3 ;-)).

Remy