on 6/11/01 12:46 PM, "Gary Lawrence Murphy" <[EMAIL PROTECTED]> wrote:
> yes, or at least, I believe so ;) In the field, my deployed app must
> handle index page requests at a concurrency level of 40, with
> turnaround times of only a few seconds.
>
> I really don't know ab that well (at the source level) but I'd expect
> it would sit on a thread's connection until it gets a response, only
> what appears to be happening is that it gets disconnected and moves on
> to the next, either due to this exception, or this is what is causing
> it.
>
> I've run this same test on plain tomcat jsp webapps without receiving
> this stacktrace, but let me just sit on it a bit and see if I can get
> more detail -- I mostly wanted to know if anyone else gets a
> stacktrace when using rapid accesses through using ab. As I mentioned
> before, the concurrency does not appear to bother the app, only when
> more than one request comes down the same ab thread.
Using ab, John M. did some testing of Scarab (Turbine/Velocity) and was
getting 60+ connections/second on a IBM Thinkpad 700mhz box with everything
running locally and no problems at all.
Also, based on the URI that you are requesting, what really happens is that
ab hits the url, the server sends a 302 redirect back (in order to try to
set the cookie) and then ab will make another request for the page. Maybe
that is what is screwing things up?
Thanks,
-jon
--
"Open source is not available to commercial companies."
-Steve Ballmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
