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 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 y
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 lb
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
Hi Filip~
That is an interesting possible solution (seems easy too). I will give that a
try. Thank you for the quick response. Cheers!
- Original Message
From: Filip Hanik - Dev Lists
To: Tomcat Users List
Sent: Wednesday, June 10, 2009 1:57:26 PM
Subject: Re: Consequences of
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
Thep
