You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2011/08/29 12:47:37 UTC
[jira] [Created] (DERBY-5394) Reduce chance of OOME with
XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low
memory suite
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
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
[jira] [Updated] (DERBY-5394) Reduce chance of OOME with
XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low
memory suite
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-5394:
--------------------------------------
Fix Version/s: (was: 10.8.2.0)
10.8.2.1
> 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.8.2.1, 10.9.0.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
[jira] [Closed] (DERBY-5394) Reduce chance of OOME with
XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low
memory suite
Posted by "Kristian Waagan (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-5394.
----------------------------------
Closing issue, no issues seen after the fix was applied.
The fix committed under this issue was a work-around, not a proper fix addressing the general root cause.
> 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.8.2.1, 10.9.0.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DERBY-5394) Reduce chance of OOME with
XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low
memory suite
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (DERBY-5394) Reduce chance of OOME with
XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low
memory suite
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-5394:
-----------------------------------
Attachment: derby-5394-1a-execute_last.diff
Attaching patch 1a, which makes the XAMemTest be executed last in the low-mem suite.
I've observed a runtime of 46 and 22 minutes for the low-mem suite. It now dropped (back) to around 12 minutes.
Committed to trunk with revision 1162737.
> 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
> 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