Thanks Dumindu. I've opened an issue in Jira, and I've been looking at the code a bit more, and I think the issue is a bit more complex. I'll move the discussion to the dev-list.
-Ben > From: Dumindu Pallewela <[EMAIL PROTECTED]> > Date: Wed, 20 Feb 2008 11:39:58 +0530 > To: <[EMAIL PROTECTED]> > Cc: Apache AXIS C Developers List <[EMAIL PROTECTED]>, Apache AXIS C > User List <axis-c-user@ws.apache.org> > Subject: Re: [Axis2C] mod_axis2 service shutdown problem > > Hi Ben, > > On Feb 20, 2008 1:40 AM, Ben Wyckoff <[EMAIL PROTECTED]> wrote: > <snip> >> Has anyone else run into this issue? Is anyone trying to allocate resources >> that have to be freed? (In particular, I'm opening a database, and I need to >> properly close it - I can't just rely on the OS to free memory or close file >> handles.) > </snip> > > This seems to be a problem with mod_axis2. Although the memory > allocated with apr_pools will get free'd eventually without free > functions being called, in order to free up other resources, we need > to register relevant free functions to pool cleanup of a pool which > has resource's lifetime. Please add a jira issue. > > The attached patch should solve this issue when shared memory is not > used. I'm not sure if it works when shared memory is used. Hope that > someone familiar with axis2c shared memory implementation will look > further into it. > > Regards, > Dumindu. > > -- > Dumindu Pallewela > http://blog.dumindu.com > GPG ID: 0x9E131672 > > WSO2 | "Oxygenating the Web Service Platform" | http://wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
