Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of henri.gomez@gmail.com
 designates 209.85.223.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51C98AF2.7070403@christopherschultz.net>
References: 
 <CALyUpY1p37Z3D=-m8H5cg=B1gEq2uAH4L7qG1=t1kWCegDw4jg@mail.gmail.com>
	<51C87E28.8010407@christopherschultz.net>
	<CALyUpY03bVAGnLcU3w82JHxOVXTDewBq4rHk29Ua9Z_zOaKFqQ@mail.gmail.com>
	<51C98AF2.7070403@christopherschultz.net>
Date: Tue, 25 Jun 2013 22:11:17 +0200
Message-ID: 
 <CALyUpY1yrjcHeW+1d1+t9deKOAEN+x9OfeSnGbW17pQARCZTTw@mail.gmail.com>
Subject: Re: mod_jk, JSESSION_ID and load-balancing
From: Henri Gomez <henri.gomez@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=bcaec51866dcbe915504e0002186

--bcaec51866dcbe915504e0002186
Content-Type: text/plain; charset=ISO-8859-1

Hi Christopher

I don't have access to code inside application, I'm using stock Sonatype
Nexus OSS who use Shiro internally to manage (and regenetate JSESSIONID
cookie), loosing jvmRoute contents.

See https://issues.sonatype.org/browse/NEXUS-5756

We could told mod_jk to use another cookie but I think Tomcat allways
append jvmRoute content to cookie JSESSIONID.

That's why Rainer and I discussed about mod_jk to generate and inject
another cookie and use it to maintain sticky affinity.
It will be an even better solution for large cluster of Tomcat behind
HTTPd/mod_jk, especially when instance are automatically provisionned from
template since we don't have to set jvmRoute in server.xml for each
instance.

But I may be wrong and may be Tomcat 7 could inject jvmRoute in another
cookie ?

Cheers


2013/6/25 Christopher Schultz <chris@christopherschultz.net>

> Henri,
>
> On 6/25/13 2:33 AM, Henri Gomez wrote:
> >> Henri,
> >> This sounds more like a question for the users list. Cross-posting to
> >> re-locate. See more below...
> >
> >
> > I used dev list because question was also about updating mod_jk code.
> >
> >> Is is important to retain the original JSESSIONID, or do you only want
> >> to retain the jvmRoute information? I would think you'd want both.
> >
> > jvmRoute should be kept in JSESSIONID as mod_jk load-balancing use it to
> > dispatch requests to proper Tomcat :)
>
> Of course! But it sounded like both Tomcat and Shiro generate a
> JSESSIONID but you were only worried about Tomcat's /jvmRoute/ (and not
> the rest of the session). I'm assuming that you want to maintain both
> session ids simultaneously.
>
> Assuming you want to retain both at the client, why not simply change
> the name of the cookie for Tomcat (or Shiro)?
>
> -chris
>
>

--bcaec51866dcbe915504e0002186--