You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Ye...@intercomponentware.com on 2003/09/08 11:32:17 UTC

Urgent !!! Problem to get TOMCAT/4.1.24 cluster running with sticky session support.

Hello , I still have no idea what could I do to get apache-tomcat cluster 
up'n'running.

Current problem is that browser session got right workerid added 
JSESSIONID=19E9FD015AF34C5181322F3FEF37B0D6.tomcat-worker-01, but sends 
request for processing to all tomcat nodes using round-robin. So tomcat 
got the session lost.


log file , JSESSIONID is the same but two tomcat hosts process it.

tomcat1:
2003-08-29 16:49:26 RequestDumperValve[Standalone]: 
cookie=JSESSIONID=19E9FD015AF34C5181322F3FEF37B0D6.tomcat-worker-01




tomcat2:
003-08-29 16:50:10 RequestDumperValve[Standalone]: 
header=cookie=JSESSIONID=19E9FD015AF34C5181322F3FEF37B0D6.tomcat-worker-01; 


this could work if session is replicated on all tomcat servers but not in 
a current state.

So the same round-robin problem like before.
(((



Any idea will be highly appreciated,

Yefym


RE: Urgent !!! Problem to get TOMCAT/4.1.24 cluster running with sticky session support.

Posted by Filip Hanik <ma...@filip.net>.
have you tried http://cvs.apache.org/~fhanik/

Filip

> -----Original Message-----
> From: Yefym.Dmukh@intercomponentware.com
> [mailto:Yefym.Dmukh@intercomponentware.com]
> Sent: Monday, September 08, 2003 2:32 AM
> To: Tomcat Users List
> Subject: Urgent !!! Problem to get TOMCAT/4.1.24 cluster running with
> sticky session support.
>
>
> Hello , I still have no idea what could I do to get apache-tomcat cluster
> up'n'running.
>
> Current problem is that browser session got right workerid added
> JSESSIONID=19E9FD015AF34C5181322F3FEF37B0D6.tomcat-worker-01, but sends
> request for processing to all tomcat nodes using round-robin. So tomcat
> got the session lost.
>
>
> log file , JSESSIONID is the same but two tomcat hosts process it.
>
> tomcat1:
> 2003-08-29 16:49:26 RequestDumperValve[Standalone]:
> cookie=JSESSIONID=19E9FD015AF34C5181322F3FEF37B0D6.tomcat-worker-01
>
>
>
>
> tomcat2:
> 003-08-29 16:50:10 RequestDumperValve[Standalone]:
> header=cookie=JSESSIONID=19E9FD015AF34C5181322F3FEF37B0D6.tomcat-w
> orker-01;
>
>
> this could work if session is replicated on all tomcat servers but not in
> a current state.
>
> So the same round-robin problem like before.
> (((
>
>
>
> Any idea will be highly appreciated,
>
> Yefym
>
>