[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthick Sankarachary resolved ODE-576.
---------------------------------------
Resolution: Invalid
The deleteProcessDAO and createProcessDAO methods of BpelProcess go hand in
hand. In other words, you use the former in conjunction with the latter. We
re-create the process DAO if and only If the GUIDs don't match. If they do
match, we do nothing.
When you undeploy a process, we do clean up its DAO objects. And, that happens
through the following function:
org.apache.ode.bpel.engine.BpelServerImpl.cleanupProcess(QName).
> ProcessDaoImpl objects get leaked when using in-memory-processes
> ----------------------------------------------------------------
>
> Key: ODE-576
> URL: https://issues.apache.org/jira/browse/ODE-576
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Environment: n/a
> Reporter: Ciaran Jessup
> Attachments: InMemoryProcessesLeakMemory.patch
>
>
> It seems that when I deploy and un-deploy in-memory processes ProcessDaoImpl
> objects stored in the __StateStore field of the BpelDAOConnectionFactoryImpl
> object are being left around.
> Over the course of several tens/hundreds of deployments the memory contained
> in these objects mounts up substantially :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
