Hi Igor, Thanks for reporting. Will have a look at this.
regards sathwik On Fri, Sep 26, 2014 at 10:27 PM, Igor Vorobiov (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/ODE-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Igor Vorobiov updated ODE-1020: > ------------------------------- > Attachment: heap_dump.png > > > Deployment memory leak > > ---------------------- > > > > Key: ODE-1020 > > URL: https://issues.apache.org/jira/browse/ODE-1020 > > Project: ODE > > Issue Type: Bug > > Components: Deployment > > Affects Versions: 1.3.6 > > Reporter: Igor Vorobiov > > Attachments: heap_dump.png > > > > > > There is deployment memory leak when we redeploy process(e.g. DynPartner > from ode examples). > > To reproduce need to do redeployment of the process: > > 1. deploy DynPartner-1 > > 2. deploy DynPartner-2 > > 3. deploy DynPartner-3 ... > > 4. run GC in JProfiler. > > In JProfiler we can see that after each redeployment memory is allocated > but after running GC it is not released. > > From attached heap dump we can see that most of the memory is allocated > for org.apache.ode.store.DeploymentUnitDir._docRegistry where wsdl is > parsed. > > Even after undeploy memory is not released. > > The problem became critical when we deployed 250 different processes > where each process has 3-4 wsdl files. All these processes consumed about > 700mb memory. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
