httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27869] - stopping and starting httpd again immediately causes bind() to fail
Date Fri, 26 Mar 2004 13:11:38 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27869>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27869

stopping and starting httpd again immediately causes bind() to fail





------- Additional Comments From trawick@apache.org  2004-03-26 13:11 -------
>Also why SO_REUSEADDR option on socket can't be used?

This option is already used.  On most platforms (including everywhere that
worker MPM runs), SO_REUSEADDR does not allow an app to bind to a port that some
other process still has a listening socket on.  It only allows an app to bind to
a port where there are still TCP connections in terminating states (e.g.,
TIME_WAIT) which were established while some app was bound to the port.

How long is it taking the Apache processes to fully shut down in your
environment before Apache can successfully re-initialize?  Is anything written
to error log during shutdown?

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message