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
Rainer Jung wrote:
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.
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
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
Greetings~
I would like to reuse the JSESSIONID route betweened clustered tomcats... and
I'm wondering if there are negative consequences for doing so.
We have the following setup:
2 data centers... (d1 / d2)
2 apache mod_proxy_balance(ad1, ad2)
4 tomcat servers (td101, td102, td201,
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
Filip
1:57:26 PM
Subject: Re: Consequences of Reusing Clustered JSESSIONID
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
