ccept"
>>>> the
>>>> sessionid, I would expect it to create a new session (and a new
>>>> sessionid) using the correct local route.
>>>>
>>>> Do you use emptySessionPath in the connector configuration inside
>>>> se
On 19/05/2010 18:48, JohnRiley wrote:
>
> Right on target. I noticed that it was the emptySessionPath="true" that
> messed things up for me. When I removed it I got back to the wanted
> behavior. However, the emptySessionPath is needed since we are using
> mod_rewrite to change the url:s of the ba
On 19.05.2010 20:12, JohnRiley wrote:
Ok, even if I execute a jsp-page in tomcat root and get a cookie with path=/
I get this problem so it has nothing to to with sharing sessions between
applications or cookie not reaching it correctly. Things just seems to stop
working properly when I add emp
ionPath in the connector configuration inside
>> server.xml?
>>
>> Can't you add a simple servlet filter overwriting the JSESSIONID cookie
>> if it's route doesn't match the local route?
>>
>> Regards,
>>
>> Rainer
>>
>>
egards,
>
> Rainer
>
> ---------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://old.n
On 19/05/2010 01:18, Steve Yates wrote:
> G'day John, the strategy I would employ in your particular case would be
> to utilise the JvmRouteBinderValve. Now the JvmRouteBinderValve was
> designed to be used within a clustered environment I cannot see why it
> cannot be configured stand-alone to sim
G'day John, the strategy I would employ in your particular case would be
to utilise the JvmRouteBinderValve. Now the JvmRouteBinderValve was
designed to be used within a clustered environment I cannot see why it
cannot be configured stand-alone to simply detect for an incorrect route
and modify
On 18.05.2010 12:35, JohnRiley wrote:
Hi,
We are load balancing 3 non-clustered tomcat 6.0 servers with the mod_jk
connector in apache 2.0. We have sticky sessions enabled and it works fine
until one of the servers goes down. What happens then is that it start
round-robin between the other two
On 18/05/2010 11:35, JohnRiley wrote:
>
> Hi,
>
> We are load balancing 3 non-clustered tomcat 6.0 servers with the mod_jk
> connector in apache 2.0. We have sticky sessions enabled and it works fine
> until one of the servers goes down. What happens then is that it start
> round-robin between th
server that is down for maintenance is back up again.
Do we really have to setup the tomcats in a cluster to accomplish this?
Best Regards
John Riley
--
View this message in context:
http://old.nabble.com/mod_jk-session-stickiness-on-failover-tp28594156p28594156.html
Sent from the Tomcat - User
10 matches
Mail list logo