Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1042060820.1246407407320.JavaMail.jira@brutus>
Date: Tue, 30 Jun 2009 17:16:47 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1099) Investigate why stress.multi can get
 OutOfMemoryError when not configured to connect to the database properly
In-Reply-To: <512554088.1142038867976.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dag H. Wanvik updated DERBY-1099:
---------------------------------

    Issue Type: Bug  (was: Test)

> Investigate why stress.multi can get OutOfMemoryError when not configured to connect to the database properly
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1099
>                 URL: https://issues.apache.org/jira/browse/DERBY-1099
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.2.1.6
>            Reporter: Deepa Remesh
>            Priority: Minor
>
> On certain platforms/jvms, stress.multi gets OutOfMemory error when the test fails to get a connection because of wrong database url. The reason for the memory error needs to be investigated. This issue was found in DERBY-956 and more details and list of platforms can be found in http://issues.apache.org/jira/browse/DERBY-956
> To repro, build derbyTesting.jar by changing the url in the test's properties files (init.properties and run.properties) to a wrong syntax and run the test stress/stress.multi.

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