pache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Limit-Num-Requests-tf2858769.html#a7988094
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
> From: adamle [mailto:[EMAIL PROTECTED]
> I thought of maybe putting a filter on the certain url
> pattern that I want,
> but instead of turning back the user, I could put his thread
> to sleep for
> aset amount of time and have him try again. Hopefully by
> then some of the
> earlier threads
--
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message
> From: adamle [mailto:[EMAIL PROTECTED]
> I am looking for a solution that for a certain url pattern
> only allows a
> certain number of requests to be serviced at the same time.
> This would
> solve my problem, while not affecting servicing lighter pages.
Makes sense.
If you can stand for y
be applying sticking plaster to a broken leg because you're
> not willing to consider the real problem.
>
> - Peter
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional command
> From: adamle [mailto:[EMAIL PROTECTED]
> While testing the site with JMeter if I put 25 users in a
> thread group and
> hit the above url concurrently I kill my tomcat instance.
What's the error? Do you run out of memory, for example? How much
memory have you allocated to the JVM?
> I'm loo
Adam.
--
View this message in context:
http://www.nabble.com/Limit-Num-Requests-tf2858769.html#a7987047
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To
