Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 29 Aug 2011 11:13:37 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2058837716.2850.1314616417814.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1110353662.2808.1314614857989.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5394) Reduce chance of OOME with
 XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low
 memory suite
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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