[jira] Reopened: (ODE-576) ProcessDaoImpl objects get leaked when using in-memory-processes

["Ciaran Jessup (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ciaran Jessup reopened ODE-576:
-------------------------------


Based on my comments above, the BpelConnectionDaoImpl instance that the 'delete' occurs on, is different to that which the 'create' occurs on, so the 'remove' that happens to the internal 'store' is happening on the JPA instance not the memdao instance, personally I've not got a clue what this means, but there *is* a leak there, sadly with the easter close down I can't get a screen shot to show you the before + after reference graphs w GC root routes highlighted, but its a very easy to find memory leak, just do multiple deply + un-deploy cycles of in-memory processes, you will see the _Store references in the BpelConnectionFactoryImpl object increase by one for each deployment, and never decrease.....

> 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.