[
https://issues.apache.org/jira/browse/DERBY-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan resolved DERBY-5394.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.8.2.0
10.9.0.0
Merged fix to the 10.8 branch, hoping there will be another RC.
I don't plan to do more on this issue now, but for later, and maybe for similar
cases, it should be investigated if using a decorator that shuts down the
database (and possibly then engine?) addresses the problem.
> Reduce chance of OOME with
> XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low memory
> suite
> -------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5394
> URL: https://issues.apache.org/jira/browse/DERBY-5394
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.9.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.9.0.0, 10.8.2.0
>
> Attachments: derby-5394-1a-execute_last.diff
>
>
> See thread on derby-dev: "Problems with junit-lowmem" (29th of August 2011).
> The test XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded
> doesn't release all the memory it uses and causes either excessive GC
> activity (and a much longer run time) or an OOME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
