ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafal Rusin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-639) Memory leak in InMem DAO
Date Fri, 06 Nov 2009 21:13:36 GMT

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

Rafal Rusin commented on ODE-639:

What's up with this comment? 
memdao-dumper was just for diagnosing leak. For actual commits, please check subversion commits.

BTW. This issue is fixed. If you have some problems with it, please reopen. 

> Memory leak in InMem DAO
> ------------------------
>                 Key: ODE-639
>                 URL: https://issues.apache.org/jira/browse/ODE-639
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.3.2
>         Environment: any
>            Reporter: Rafal Rusin
>            Assignee: Rafal Rusin
>         Attachments: memdao-dumper.patch
> In Memory DAO, there is a cleanup strategy, which assigns TTL 10 min. for in-memory instances.

> I works for 1 in-memory process, but for 2 or more, there are cases when it doesn't do
> I figured out that cleaning strategy in bpel-runtime/src/main/java/org/apache/ode/bpel/memdao/ProcessDaoImpl.java
holds a static _lastRemoval field, which is updated globally. But if there are >1 in-mem
processes, it may cause only one to do cleanup. 
> A simple patch, which removes static declaration solves problem, because then, cleanup
is done separately for each process. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message