That's not a bad idea, I will look into.
Thanks again for the help.
Peter Crowther wrote:
>
>> 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
> 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
Thanks for the idea Peter.
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 will have finished and he can
> 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
Thanks for the reply Peter.
I am caching these pages after they are processed, but because of the nature
of the application, they are many different kinds of these pages.
Tomcat does not even throw an exception, I have allocated 128-356 mb memory.
It just dies and does not response to requests.
> 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
