[
https://issues.apache.org/jira/browse/ODE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jürgen Schumacher updated ODE-381:
----------------------------------
Attachment: r603090.patch
Diff of revision 63090 in branch_1.x
> In trunk, time-to-live in in-memory-DAO is not configurable like in 1.x branch
> ------------------------------------------------------------------------------
>
> Key: ODE-381
> URL: https://issues.apache.org/jira/browse/ODE-381
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3
> Environment: Win32, Java 1.5, Eclipse Equinox runtime.
> Reporter: Jürgen Schumacher
> Attachments: r603090.patch, r603265.patch
>
>
> Hi,
> Revisions 603090 and 603265 introduced a configuration property for the
> in-mem-mex-timeout (see also
> http://ode.markmail.org/search/?q=inmem.ttl#query:inmem.ttl+page:1+mid:7ldgsgjuprk7itvl+state:results).
> It seems that these patches did not make it intto the trunk, at least the
> classes BpelDAOConnectionImpl and ProcessDaoImpl in
> engine\src\main\java\org\apache\ode\bpel\memdao have the TIME_TO_LIVE
> constants again, and we experienced memory problems again. I tried to apply
> the patch to the current trunk, but there have been some design changes so
> that I did not succeed in adapting the changes. For your convenience, I will
> attach the original diffs from the two revisions. I have seen ODE-295 and
> the related issues, but I think that this configuration property is still
> relevant, because at least in BpelDAOConnectionImpl the constant is used in
> the only place where MExes are removed from _mexList/_mexStore (apart from
> rollbacks, which do not occur usually).
> Excuse me if I missed something that would be the correct solution.
> Yours,
> Juergen.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
