[users@httpd] Apache 2 - Visit based connection limiting.

[Jason Czerak <ja...@minn.ppdi.com>]

What I wish to accomplish is a visit based connection limiting. A visit
defined as an IP address (user) that is active within the site, but not
idle for X time (say, 30 minutes). 

Modules like mod_throttle, bw_mod, mod_bandwidth, primarily do bandwidth
based limits and connection based.  bw_mod, does do a nice redirect once
we the limit is reached.  But I need to take this a step further.

I'm looking for something that tracks what IP's are in use, that are not
idle for X time, and allow them priority over other IPs. Should an IP be
idle for X time, we'll removed them from the list. If we are at our max
visitors, a redirect will be issued to a nice page that explains we are
at a high load, try again; to all users that are not listed. 

The idea here it to ensure visitors that are already on the site have an
enjoyable experience, while new visitors during peek hours get a nice
message saying try back later. With bw_mod, users they are already
viewing content COULD get this message in the middle of their "visit". I
want to avoid this.

I rather putz along the highway at 15mph while other cars are not
allowed to merge onto the highway (those traffic lights on the on
ramps), as apposed to every one any their mother merging on at the same
time creating grid lock. :) right?

I have asked the developers if it is possible to implement this on the
code. Apparently with Weblogic, and the way this application is
designed, it won't be possible. So I'm looking for a server solution.

Technical details:

Currently, we have a content based application.
Weblogic 8.1 SP3
Dual Xeon HT 3ghz 6gig's ram. (not my fault this machine is freaking
slow, I arrived after the fact)
DS3 up link
RedHat ES 3 AS (not my fault we are using RH, I was contracted in after
the fact)

For the few weblogic people that might have some questions about our
weblogic setup. We are just running one jrocket JVM with 2 gig heap. CPU
cycles are the bottle neck. Bandwidth is not. If we run a local cluster
to use more ram, we suspect that CPU will still be the bottle neck.
Also, our application experiences some funky stuff in a cluster.

As for hardware, We are ordering more hardware. Correct hardware.
4xAMD64 and 10gig's ram. And something not RedHat. :) In the mean time
I'm looking for a solution to improve site experience.

Any other suggestions would be great.

--
Jason Czerak



______________________________________________________________________
This email transmission and any documents, files or previous email
messages attached to it may contain information that is confidential or
legally privileged. If you are not the intended recipient or a person
responsible for delivering this transmission to the intended recipient,
you are hereby notified that you must not read this transmission and
that any disclosure, copying, printing, distribution or use of this
transmission is strictly prohibited. If you have received this transmission
in error, please immediately notify the sender by telephone or return email
and delete the original transmission and its attachments without reading
or saving in any manner.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org