[
https://issues.apache.org/jira/browse/ODE-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171337#comment-14171337
]
Sathwik Bantwal Premakumar commented on ODE-1020:
-------------------------------------------------
The problem seems to be in the deactivate() method in BPELProcess. This method
is responsible to deactivate the service endpoints and destroy the Axis Service.
The block of code is enclosed by a condition that, if the process is in an
Active state then only proceed for deactivation of endpoints.
In our current scenario, which involves redoployment of a process; The flow
works in such a way that an Active version of the process is Retired and then
the new version is Activated. Deactivation of endpoints is invoked during the
Retire phase and since there is a condition check for Active state of the
process, deactivation never happens as the process state is already set to
Retired and hence one can see all the Axis Sevice piling on.
This condition check for Active state doesn't make sense for this scenario.
> 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
> Assignee: Sathwik Bantwal Premakumar
> Fix For: 1.3.7, 1.4
>
> Attachments: DeploymentService-soapui-project.xml, heap_dump.png,
> memLeak2.png, memLeak3.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)
