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] Assigned: (ODE-538) Letting Go Of Retired Processes
Date Tue, 03 Mar 2009 23:20:56 GMT

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

Karthick Sankarachary reassigned ODE-538:
-----------------------------------------

    Assignee: Karthick Sankarachary

> Letting Go Of Retired Processes
> -------------------------------
>
>                 Key: ODE-538
>                 URL: https://issues.apache.org/jira/browse/ODE-538
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>            Reporter: Karthick Sankarachary
>            Assignee: Karthick Sankarachary
>             Fix For: 1.3
>
>
> In the event a process is marked for retirement, a best-effort must be made to release
all of its resources from memory. Currently, a retired process stays in memory forever. As
a result, the memory footprint of a process rises monotonically with each successive deployment,
even if previous versions are retired. 
> The object models that dominate a process' footprint are those of BPEL, which is managed
by ODE, and WSDL, which is managed by Axis2. To expedite garbage collection of the BPEL graph,
we must try to recursively clear the entire tree that is rooted underneath the OProcess object.
To facilitate garbage collection of the WSDL forest, we must release the schema list and definition
for every AxisService that the process provides.

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


Mime
View raw message