db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1099) Investigate why stress.multi can get OutOfMemoryError when not configured to connect to the database properly
Date Tue, 11 Apr 2006 23:40:22 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1099?page=all ]

Mike Matrigali updated DERBY-1099:
----------------------------------

    Component: Test

> Investigate why stress.multi can get OutOfMemoryError when not configured to connect
to the database properly
> -------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1099
>          URL: http://issues.apache.org/jira/browse/DERBY-1099
>      Project: Derby
>         Type: Test

>   Components: Test
>     Versions: 10.2.0.0
>     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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message