From modules-dev-return-1694-apmail-httpd-modules-dev-archive=httpd.apache.org@httpd.apache.org Tue Apr 29 17:12:14 2008 Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@locus.apache.org Received: (qmail 93328 invoked from network); 29 Apr 2008 17:12:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Apr 2008 17:12:14 -0000 Received: (qmail 63365 invoked by uid 500); 29 Apr 2008 17:12:14 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 63348 invoked by uid 500); 29 Apr 2008 17:12:14 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 63152 invoked by uid 99); 29 Apr 2008 17:12:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Apr 2008 10:12:13 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cesarbs@gmail.com designates 74.125.46.153 as permitted sender) Received: from [74.125.46.153] (HELO yw-out-1718.google.com) (74.125.46.153) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Apr 2008 17:11:28 +0000 Received: by yw-out-1718.google.com with SMTP id 9so26412ywk.84 for ; Tue, 29 Apr 2008 10:11:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=WCnRNCWIE81jVz4jhGm1ej1jw6rilV46Rl98wnrHkoU=; b=kjeBiVndh+vQuRqujO3vT4GF0vrY0T01omVEhB+mNxPv/BS6caxALQHWliHe3cbymi8NwvIbRWt17R3Zz3DtPzHYKWU0ikLTEALcRxoywjZLODHIfZA1KpDUaJMh1I08kHni3LipPIzTxI//eCe7D69nN8Yym/nK1geTFRW7zzc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WOlfBNR1tczBk9ZmmDmJOerP/W7wWwNjHFyBHlO/ehm+yqIxXjXCy4JxiP7eHQzSwjDnSelwEUdDGJ9N7Z0m3sJGm2wiw3HAKhNNEdMFNwmciQEDIVSxlnHIZToYJaR71H5AHZk0hYT+0nyqHe514gLbeC8W/oIj3ddEu0DGWtI= Received: by 10.142.141.21 with SMTP id o21mr507814wfd.199.1209489072466; Tue, 29 Apr 2008 10:11:12 -0700 (PDT) Received: by 10.142.224.21 with HTTP; Tue, 29 Apr 2008 10:11:12 -0700 (PDT) Message-ID: Date: Tue, 29 Apr 2008 14:11:12 -0300 From: "=?ISO-8859-1?Q?C=E9sar_Leonardo_Blum_Silveira?=" To: modules-dev@httpd.apache.org Subject: Re: Pool cleanups on Windows Server 2008 In-Reply-To: <48175537.2020202@rowe-clan.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <48174A3C.6000703@rowe-clan.net> <48175537.2020202@rowe-clan.net> X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Apr 29, 2008 at 2:04 PM, William A. Rowe, Jr. wrote: > C=E9sar Leonardo Blum Silveira wrote: > > > On Tue, Apr 29, 2008 at 1:18 PM, William A. Rowe, Jr. > > wrote: > > > > > C=E9sar Leonardo Blum Silveira wrote: > > > > > > > > > > Hello, > > > > > > > > The application we develop at the company where I work is presentin= g > > > > some problems in Windows Server 2008. Basically, the pplication > > > > consists of a bunch of Apache modules that serves our purposes. For > > > > what we have observed so far, pool cleanups reigstered for the serv= er > > > > pool in the post config hook are not always run on restart events. = It > > > > seems to be totally random: sometimes the cleanups are run, sometim= es > > > > not. > > > > > > > > > > > Can you define "restart"? > > > > > > > Sorry. It's on -k restart. > > > > Then are you certain these are not run? The reason I ask is that there = are > two sets of cleanups... > > * in the parent process, the process pool cleanup will not run till the > server is entirely stopped. The others should run normally. > > * in the old child process, the cleanups will not run until the various > requests have completed. This means the new child's setups should be > expected to run before the old child process cleanups are run. > Ok, now I got into some doubts. What I'm doing is registering a cleanup for the pool which is passed as the first argument to my post config hook. Is that the parent's or the child's pool? Thank you for your help, --=20 C=E9sar L. B. Silveira