[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700162#action_12700162
]
Ciaran Jessup commented on ODE-576:
-----------------------------------
Hi Karthick,
Unfortunately this patch also doesn't work, this time it is because the
_processes array which you're relying on being populated with the process to
determin its in-memory state is being cleared out (
_processes.keySet().removeAll(undeployed); ) in the ProcessStoreImpl.undeploy
method a couple of lines before that method actually fires the UNDEPLOYED event
to which you've associated the cleanup code.
When that UNDEPLOYED event is process, the line :
_bpelServer.cleanupProcess(pse.pid, pconf.isTransient());
Falls over with a NPE as 'pconf' is now a null reference.
Hope this helps
- Cj.
> 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,
> process-dao-cleanup.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.
