Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 18043 invoked from network); 1 Apr 2008 03:18:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Apr 2008 03:18:26 -0000 Received: (qmail 3175 invoked by uid 500); 1 Apr 2008 03:18:26 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 3161 invoked by uid 500); 1 Apr 2008 03:18:25 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 3146 invoked by uid 99); 1 Apr 2008 03:18:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2008 20:18:25 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.68.5.16] (HELO relay02.pair.com) (209.68.5.16) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 01 Apr 2008 03:17:36 +0000 Received: (qmail 16697 invoked by uid 0); 1 Apr 2008 03:17:54 -0000 Received: from unknown (HELO ?10.100.1.213?) (unknown) by unknown with SMTP; 1 Apr 2008 03:17:54 -0000 X-pair-Authenticated: 222.165.132.170 Message-ID: <47F1A960.9030009@wso2.com> Date: Tue, 01 Apr 2008 08:47:52 +0530 From: Uthaiyashankar User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: Apache AXIS C User List Subject: Re: Memory leak in mod_axis2? References: <6463f4210803281238l797d1321ja1e2e2922e7b497a@mail.gmail.com> <47EEFF8A.4090407@wso2.com> <6463f4210803310728k4c4d246avb731777fb28ea920@mail.gmail.com> In-Reply-To: <6463f4210803310728k4c4d246avb731777fb28ea920@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > > No, MaxRequstsPerClient is set to 0, and yes, I understand that I can > use this to kill old children processes with accumulated memory leaks > and start new fresh ones, but you know, using MaxRequestPerClient is > kind of cheating :) - there should not be memory leaks in the > mod_axis2 in the first place... > I doubt whether it is a memory leak. When using mod_axis2, memory management is done by apache apr. Memory is released only when pools are destroyed. Memory will not be released when calling AXIS2_FREE. (axis2_module_free is implemented in mod_axis2.c:412 and it is an empty method unless the pool associated with is global shared pool). When to destroy a pool is in the control of apache. MaxRequestPerClient is a cheating way to force apache to release the pool :) Regards, Shankar > > Thank you, > > alex. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-c-user-help@ws.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-user-help@ws.apache.org