Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Date: 20 Feb 2004 00:50:52 -0000
Message-ID: <20040220005052.15706.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 27079]  -
    On client restart server no longer responds

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=27079>.
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=27079

On client restart server no longer responds


------- Additional Comments From trawick@apache.org  2004-02-20 00:50 -------
>Would this still be true if we only have one client?.  
>We are using the worker MPM and have it configured to allow only 
>1 client with many threads

We call that "one child process" instead of "one client."

Yes, it is true with one many-threaded child process too.  In fact, with a
single child process you guarantee that the child process being whacked is
holding the accept mutex.  The parent sees that it needs to create a new child
process, but the listener thread in the new child process blocks waiting to
obtain the accept mutex that was held by the whacked child process.

(This use of the accept mutex on modern AIX is only when there is more than one
listening socket.  But you have more than one listening socket.)

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