db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1099) Investigate why stress.multi can get OutOfMemoryError when not configured to connect to the database properly
Date Wed, 01 Jul 2009 00:16:47 GMT

     [ 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.


Mime
View raw message