Hi
Thx for the reply
We need to Configure TOMCAT 's ROOT to APCHE2.x for Load balancing.
Problem
Load on this single TOMCAT is building up the CPU for 100% ,as the
subscribers are increasing.
Solution
We need to bring in the Load Balancer with Multiple TOMCAT /APACHE2.x
server.
Hence we need multiple TOMCAT with ROOT being able to configure to a
APCHE 2X http server.
Is this possible ?
with regards
Karthik
Oscar Mechanic wrote:
Hi
Sorry not going to answer the question you asked but have worked on this
type of solution many times.
The problem is your redirects if a virus gets on the network it will
clobber the server as it tries to get outside. All the client MS updates
is over HTTP that will clobber it.
You need to limit the number of simultaneous connections per client.
That is only allow 5 connections to be redirected to the web app in say
30 seconds. Else no matter what horse power you put behind it will
always be effected by DoS attacks. I don't think cisco routers are that
clever.
You can do this the cheap way and get the HTTP_REQUESTER IP stick em in
a hashtable with a datestamp. But this is just a patch not a fix.
Because it can still be used to clobber the server.
I don't work for zeus and have only played with there VMWare stuff but
you may wanna try zeus.co.uk and use that to load balance and do URL
filtering. It can do fancy stuff with URLs and DNS. F5 is another one.
Regards
On Mon, 2008-03-24 at 19:00 +0530, karthikn wrote:
Hi
Thnx for the initial Reply
The Life Cycle for the WIFI custom web application for AAA is as follows.
1) User Types "www.xyz.com"
2) CISCO ROUTER Intercepts this requests and reroutes to a WEB container
as http://<IP>:<PORT> or http://<IP> Only for AAA to be processed.
[ Note: CISCO Router API's can only redirect any http requests to
specific IP / Port and not a web application
hosted on the IP as http://<IP>:<PORT>/AAAprocess ]
3) AAA processing is done in the WEB container by the application hosted
as ROOT
( Replaced original "ROOT" with custom web application ) by default.
4) Once the AAA is processed, we redirect the user to a new Window of
the browser and allow
the user to the pge requested for Originally (www.xyz.com).
Problem
Load on this single TOMCAT is building up the CPU for 100% ,as the
subscribers are increasing.
Solution
We need to bring in the Load Balancer with Multiple TOMCAT /APACHE2.x
server.
Hence we need multiple TOMCAT with ROOT being able to configure to a
APCHE 2X http server.
Is this possible ?
with regards
Karthik
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
