DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21495>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21495 ab blocks in 2.0.47 ------- Additional Comments From [EMAIL PROTECTED] 2003-07-11 11:40 ------- I can verify this problem with ab from Apache 2.1-dev on RedHat 8. Interestingly, apr_poll() hasn't changed in some time. And yet ab hasn't changed its use of socket I/O in some time either. Go figure :) Apparently the use of poll in ab is broken, as polling only for POLLIN is only going to catch failures to connect. Give this a spin (it works for me). Index: ab.c =================================================================== RCS file: /home/cvs/httpd-2.0/support/ab.c,v retrieving revision 1.126 diff -u -r1.126 ab.c --- ab.c 10 Jul 2003 19:16:35 -0000 1.126 +++ ab.c 11 Jul 2003 11:32:52 -0000 @@ -1268,7 +1268,7 @@ c->state = STATE_CONNECTING; c->rwrite = 0; new_pollfd.desc_type = APR_POLL_SOCKET; - new_pollfd.reqevents = APR_POLLIN; + new_pollfd.reqevents = APR_POLLIN | APR_POLLOUT; new_pollfd.desc.s = c->aprsock; new_pollfd.client_data = c; apr_pollset_add(readbits, &new_pollfd); I rarely use ab myself, and the only testing of it that I did personally over the last few releases has been over loopback, where I assume the connect completed synchronously and we didn't need to poll() until it completed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
