[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699579#action_12699579
]
Ciaran Jessup commented on ODE-576:
-----------------------------------
Hi Karthick,
Unfortunately your patch doesn't seem to actually do anything :)
The reason it doesn't do anything is because the new BpelEngineImpl.isInMemory
call relies on the passed process Id being stored in the _activeProcesses list
in order to determine whether or not the process is in memory or not.
Unfortunately when an UNDEPLOYED event occurs and is caught in
ODEServer.handleEvent code, this code executes:
_bpelServer.unregister(pse.pid);
_bpelServer.cleanupProcess(pse.pid);
The 'unregister' code *removes* the process from the _activeProcesses list that
is later checked transitively from within the cleanupProcess, because it is
never there, the process is never found, so it can never be checked as being
'in-memory'.
Hope this helps :)
> 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.
