ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthick Sankarachary (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-576) ProcessDaoImpl objects get leaked when using in-memory-processes
Date Thu, 16 Apr 2009 18:14:14 GMT

    [ https://issues.apache.org/jira/browse/ODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699789#action_12699789

Karthick Sankarachary commented on ODE-576:


I have updated the patch so that it does not rely on the engine to figure out whether or not
the process is "in-memory". In fact, the version that is attached right now was what I wanted
to give you initially. However, against my better judgement, it was decided that it would
not be a good idea to change the interface of the bpel server. In light of your observations,
it seems like we have no choice but to pass the "in-memory" flag from the integration layer
to the bpel server. And that is what my current patch does. I'm hoping that second time is
the charm...


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

View raw message