Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Message-ID: <4BE6A9D1.7020003@ice-sa.com>
Date: Sun, 09 May 2010 14:25:53 +0200
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: Tomcat Users List <users@tomcat.apache.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Dynamic configuration of workers
References: 
 <201675D6CE38224787808079B59D23E10505826F71@EX-IAD6-A.ant.amazon.com>
 <C581EB42-4130-4DEC-A851-A0C5C8473628@npcinternational.com>
 <201675D6CE38224787808079B59D23E1050582712E@EX-IAD6-A.ant.amazon.com>
 <4BE4890B.5050706@pidster.com>
 <201675D6CE38224787808079B59D23E105058271EA@EX-IAD6-A.ant.amazon.com>
 <4BE48CD4.7030905@pidster.com>
 <201675D6CE38224787808079B59D23E10505827200@EX-IAD6-A.ant.amazon.com>
 <4BE48E4E.2000705@pidster.com>
 <201675D6CE38224787808079B59D23E10505827229@EX-IAD6-A.ant.amazon.com>
 <4BE685D4.2050602@apache.org>
In-Reply-To: <4BE685D4.2050602@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Mark Thomas wrote:
> On 07/05/2010 23:20, Smith, Mark wrote:
>>> -----Original Message-----
>>> From: Pid [mailto:pid@pidster.com]
>>> There are a couple of linux load balancer projects that might work, if
>>> you can ditch HTTPD.  E.g. www.linuxvirtualserver.org
>> We use LVS to balance load across our Apache layers already, so I'm quite familiar with it.
>>
>> It does do what I want here, except that there are several things we need from Apache:  Access control, SSL termination, URL path based routing, etc.
>>
>> I considered using ipvsadm on the Apache box to route traffic to TomCats, but there is another EC2 specific problem:  All the routing methods LVS uses don't work on EC2 because they _ONLY_ route TCP, UDP and ICMP:
>> - Direct Routing messes with Ethernet headers.  Not a chance.
>> - Tunneling uses IP-in-IP tunneling, which is neither TCP, UDP nor ICMP. *grump*
>> - NAT gets blocked by the EC2 firewalls, which makes sense.
>> - I even tried setting up GRE tunnels; no love.
>>
>> So, yeah.  Thought of that already too.  :-)
>>
>> Anyone else have any ideas?  So far, modifying /etc/hosts looks like the best solution, even though it tips my kludge-o-meter past my comfort zone.
> 
> Take a look at mod_cluster from JBoss. I haven't looked at it for a
> while but when I saw it at ApacheCon EU last year it looked like it
> might be what you are looking for.
> 
Also, modifying /etc/hosts may not be the panacea.  I would imagine that 
e.g. mod_jk instances do not do a name resolving call at each 
transaction, and that they cache the result.


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