JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Allistair Crossley
Hi, I have setup 2 Tomcats on the same machine fronted by IIS, and used a sticky_session=1 JK (1.2.15) load-balanced setup (as printed at the foot of this email) I setup a JSP on both Tomcats that outputs the session ID. With only 1 Tomcat started, making requests to the JSP results in the same

RE: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Allistair Crossley
: JK Sticky Session Handling with Load Balancing Hi there, You're setting the sticky_session property for each worker. That's not how it works. That property is valid only for the loadbalancer and it takes a boolean value. Set it to 'True' or '1' to get the desired effect. Read http

Re: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Rainer Jung
] Sent: 18 April 2006 12:32 To: Tomcat Users List Subject: Re: JK Sticky Session Handling with Load Balancing Hi there, You're setting the sticky_session property for each worker. That's not how it works. That property is valid only for the loadbalancer and it takes a boolean value. Set

Re: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Reinhard Moosauer
worker.tomcat2.cachesize=10 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=tomcat1,tomcat2 worker.loadbalancer.sticky_session=1 -Original Message- From: Edgar Alves [mailto:[EMAIL PROTECTED] Sent: 18 April 2006 12:32 To: Tomcat Users List Subject: Re: JK Sticky Session

Re: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Edgar Alves
Users List Subject: Re: JK Sticky Session Handling with Load Balancing Hi there, You're setting the sticky_session property for each worker. That's not how it works. That property is valid only for the loadbalancer and it takes a boolean value. Set it to 'True' or '1' to get the desired

RE: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Allistair Crossley
To: Tomcat Users List Subject: Re: JK Sticky Session Handling with Load Balancing Hi again, When using two workers like that you must set the domain property for each of them for having mod_jk send the requests to the appropriate Tomcat instance. Add the following two lines to your workers

Re: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Rainer Jung
Alves [mailto:[EMAIL PROTECTED] Sent: 18 April 2006 14:36 To: Tomcat Users List Subject: Re: JK Sticky Session Handling with Load Balancing Hi again, When using two workers like that you must set the domain property for each of them for having mod_jk send the requests to the appropriate Tomcat

RE: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Allistair Crossley
. Best regards, Allistair. -Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: 18 April 2006 16:08 To: Tomcat Users List Subject: Re: JK Sticky Session Handling with Load Balancing domain: you don't need the domain attribute. Domai has the following purpose: Once you start

RE: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Allistair Crossley
:[EMAIL PROTECTED] Sent: 18 April 2006 17:10 To: Tomcat Users List Subject: RE: JK Sticky Session Handling with Load Balancing Hi, Thanks for the suggestions, that has led to a solution I think. I used the EAL valve to log inbound and outbound cookies as you suggested. Valve className