tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lataxes, Karl" <>
Subject RE: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
Date Thu, 11 Aug 2011 13:32:04 GMT
OK, I'm getting close.  On the server side, I'm adding a "Set-Cookie" header containing the
session id I want to use.  The client emulator I am using has similarly been modified to add
a "Cookie" header with the session id sent by the server, but sticky sessions are still not
working.  In the mod_jk log, there is a "searching worker for partial sessionid" reference
that contains the correct session id, but ".<worker>" was not appended.  In my
file, "sticky_session" is set to 1.  The "jvmRoute" parameters in my respective Tomcat server.xml
files are set to the workers identified in the file as well.   What do
I have to do to append ".<worker>" to the outgoing session id?

-----Original Message-----
From: André Warnier [] 
Sent: Tuesday, August 09, 2011 5:09 PM
To: Tomcat Users List
Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8

Rainer Jung wrote:
> On 09.08.2011 20:45, Lataxes, Karl wrote:
>> Our clients cannot send or process JSESSIONIDs as they are not web 
>> browsers, but proprietary equipment running embedded software that 
>> sends HTTP POST messages to a servlet on our internal network.  The 
>> servlet keeps track of sessions internally by assigning a session id 
>> which is contained within the HTTP request body.
>> I believe my best solution would be to send an additional header 
>> containing the session id with the servlet response and using that 
>> for sticky sessions.  I am working with our embedded software 
>> developers on sending this header back to the servlet during 
>> subsequent client requests to facilitate sticky sessions.  I know I 
>> will probably have to go to Apache 2.2 to accommodate this, but that 
>> was something I expected.
> Are you aware of the fact, that a cookie *is* an additional HTTP 
> header, namely the header named "Cookie"? So if you can set HTTP 
> headers to values you can define, then you *can* send cookies.

That was a much shorter way to get to the same conclusion as my earlier contribution..

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message