[
https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ciaran Jessup updated ODE-576:
------------------------------
Attachment: InMemoryProcessesLeakMemory.patch
This patch contains a 'fix' (I could completely have mis-understood the problem
please understand!) to the leaked ProcessDaoImpl object instances. It seems to
me that the BpelProcess.deleteProcessDAO has been implemented as a copy'n'paste
of the createProcessDAO and doesn't actually do anything ! Also I *think* the
dehydrate method should call into this method to get things deleted.
I've fixed it for the in-memory stuff, but I suspect there is a bigger issue
here, someone cleverer than me should probably take a look ;)
> 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.
