You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Pablo Morillas <pa...@sortes.com> on 2001/08/14 00:18:56 UTC
Control the number of request's
Hello all.
Can anyone explain me (and to all people of the list) how control the number
of request that one client can do? I'm using Tomcat 3.2.3 and if one client
with IE or NN push Reload several times, my server does one connection to
the DataBase in all the requests. Then, the Oracle 8i crash becouse the
other server creates several process, one per thread of the session of the
Tomcat. I would like to respond only the last request, and cancel the
previous one.
Is it possible with Tomcat?
And another question, are there any way to call a method of a servlet
periodicaly from the server? I would like to clean several objets that are
in the httpsession.
Thanks to all.
==================================
Pablo Morillas
http://www.sortes.com
pablo@sortes.com
==================================
Re: Control the number of request's
Posted by matt <ma...@paycom.net>.
you could create a database thread-pool. This way only a certain amount of
connections could come from any 1 server.
-m
Re: Control the number of request's
Posted by Tim O'Neil <ti...@xythos.com>.
At 03:18 PM 8/13/2001, you wrote:
>Hello all.
>
>Can anyone explain me (and to all people of the list) how control the number
>of request that one client can do? I'm using Tomcat 3.2.3 and if one client
>with IE or NN push Reload several times, my server does one connection to
>the DataBase in all the requests. Then, the Oracle 8i crash becouse the
>other server creates several process, one per thread of the session of the
>Tomcat. I would like to respond only the last request, and cancel the
>previous one.
>Is it possible with Tomcat?
It'd probably be a lot easier to simply up the Oracle configuration.
It's a little of putting the cart before the horse by attempting to
control the number of requests. If the requests exceed the capacity
of your web server the worst that happens is the excess requests get
things like 404's (I think). But an Oracle server crashing means you
probably have aspect of it's configuration set too low. Trying to
solve the problem by some how limiting the requests doesn't sound
like the optimal solution to me. You may be running the server with
default settings. Look at the config file and up whatever it is that
deals with connections to the data base and threads. I used to know
but its been a long time.