tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <rainer.j...@kippdata.de>
Subject Re: Consequences of Reusing Clustered JSESSIONID
Date Fri, 12 Jun 2009 09:46:52 GMT
On 12.06.2009 02:57, Filip Hanik - Dev Lists wrote:
> Rainer Jung wrote:
>> On 10.06.2009 22:57, Filip Hanik - Dev Lists wrote:
>>  
>>>> this is because apache a2 only has routes for td201 and td202... but
>>>> not td101... therefore it doesn't know how to handle td101.
>>>>       
>>> why don't you setup all four routes for a1 and a2.
>>> then use the mod_proxy_balancer lbset variable to set a preferred route,
>>> and problem will be solved
>>>     
>>
>> Although this will work, it will need more connections
> more connections true, but they timeout if idle
>>  and thus threads,
>>   
> not really, since idle connections will be in a polling state if you are
> using APR or NIO.
> And if using BIO, then you set a timeout, and the threads will be
> released after the timeout.
> 
>> because the routes use different connection pools.
>>
>> You could also rewrite the jvmRoute in the session id:
>>
>> http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html#Bind%20session%20after%20crash%20to%20failover%20node
>>
>>   
> sounds like a mod_jk feature, they are using proxy_balancer, is it
> available there?

I thought it's only based on cluster, jvmRoute and session IDs. How
should mod_jk come into play here?

Yes, they have to set the jvmRoute, and mod_proxy_balancer has to use
it. But apart from that?

Regards,

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message