Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 88525 invoked by uid 500); 6 Sep 2002 01:50:22 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 88512 invoked from network); 6 Sep 2002 01:50:21 -0000 Message-ID: <3D7809E6.2000800@apache.org> Date: Thu, 05 Sep 2002 18:50:30 -0700 From: Brian Pane User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020722 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: the listener thread didn't exit References: <007a01c25460$11d46140$e3008d10@little1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N David Hill wrote: >Hi all, > I am seeing log messages saying "the listener thread didn't exit". This >is coming out of the housekeeping stuff in the worker module. I am using >2.0.40 and Tru64. I *think* it is happening when the server is trying to >reduce surplus clients. > The worker MPM has known problems with process shutdown, so this part isn't entirely surprising. > On a possbilly related note, I am seeing this when whacking the server >with ab (repeatedly), and after a while seeing the server stop responding >(although in one case it seemed to come back). The server is still acception >connections, just not processing them (at least a telnet connects, but I get >no response) > This part, though, sounds like a new problem. Do you have a way to grab a stack trace of one of the stuck processes when this happens? Thanks, Brian