Andre,
We have a vast user population thats geographically dispersed, so implementing
something thru the system would be the favourable approach..
Can you point me to links on the web that explain the add on modules and their
implementation?
All,
Is there a 3rd party tool available to manage tomcat sessions and kill them
once they go rogue? We dont have an inhouse development staff, so the best
approach would be buying something off the shelf if it exists..
Thanks,
Chetan
________________________________
From: Peter Crowther <peter.crowt...@melandra.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Tue, December 15, 2009 12:07:15 PM
Subject: Re: Limit user sessions in tomcat
2009/12/15 André Warnier <a...@ice-sa.com>
> On another level, I don't quite understand yet how this squares with the
> fact that most browsers will not establish more than 2 connections with the
> same webserver at the same time. It seems a bit difficult to imagine that
> one single user can "crash" a Tomcat just by repeatedly hitting the same
> link.
>
> As far as the browser's concerned, clicking a link while a request is
pending cancels the previous request (and generally closes the socket) and
opens a new one. So it only has one connection open at any one time.
As far as Tomcat's concerned - as shown by the recent emails on the topic -
there's no way of detecting that closed socket and stopping its thread from
trying to service it. So old requests build up, unwanted but impossible to
discard until they complete or try to write something to the (closed)
socket.
- Peter
