Tom Jackson wrote:
Now how to get ab stuck and give up? I use a regular browser (mozilla), and I
try to load the same image, I hit reload like 5-7 times or so. The number of
reloads is larger than the number of maxconns per thread. There is only one
thread working.
What may be happening is that the keepalive system is expiring the thread all
by itself (one client with keepalive). Even though there is a queue, maybe
the sock and therefore the conn are being reused, giving no other requests a
chance. The last log entry indicates that the thread has processed too many
conns and is exiting. Then ab freezes. However, if I reload the page one more
time in the browser, ab starts up again.
I still think all the evidence points to a logical error of deleting a thread
and then not maintaining at least one thread (and prefer minthreads) if there
is something in the queue. This isn't a race condition, I don't think,
because it is easy to repeat this: it happens exactly the same way every
time.
So it looks like a keep-wait socket is immediately put to the head of the line
looking for more requests from the same client. If you have a web page with
50+ images, you can easily blow out any reasonable maxconns setting, or if
someone reloads a less heavy page.
Do you still get the lockup in your scenario with keepalives off? If
not, it might be a workaround until it gets fixed. If memory serves, it
would not be the first time that keepalives have been broken.
-J
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
