db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1564) wisconsin.java test failed in DerbyNet or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Date Tue, 19 Sep 2006 07:20:23 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]

John H. Embretsen updated DERBY-1564:
-------------------------------------

    Fix Version/s:     (was: 10.2.1.0)
       Derby Info:   (was: [Patch Available])

The failures described in this issue were mainly triggered by a bug in the test harness which
has been fixed in 10.2 and trunk. I am wondering if we should close this issue and open a
new one for the porting of the 10.2.0.4 wisconsin test to the 10.1 branch (I have a new patch
ready for that), and possibly one for running the wisconsin test with smallish Java heaps
(< 32 MB).

Any thoughts or objections?

Not sure what the fix version should be here, if any, so unsetting it for now...

> wisconsin.java test failed in DerbyNet or DerbyNetClient frameworks, VM for network server
got OutOfMemoryError
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1564
>                 URL: http://issues.apache.org/jira/browse/DERBY-1564
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server, Test, Regression Test Failure
>    Affects Versions: 10.2.1.0
>         Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework.
>            Reporter: Andreas Korneliussen
>         Assigned To: John H. Embretsen
>         Attachments: port-wisconsin-from-10.2.0.4-to-10.1_v1.stat, port-wisconsin-from-10.2.0.4-to-10.1_v1.zip,
wisconsin.tar.gz
>
>
> The wisconsin test failed on some Solaris (sparc) platforms during testing of the 10.2.0.4
snapshot, in either the DerbyNet or DerbyNetClient framework. 
> No output in the outfile. On some platforms the DerbyNet.err file has one message:
> Exception in thread "Thread-2" java.lang.OutOfMemoryError: Java heap space
> On some platforms the OutOfMemoryError is also (or instead) reported in the derby.log
file.
> All test machines had 2 CPUs and 2 GB of RAM.
> Here is a list of platforms where it failed:
> Java 6 (Mustang, build 91) :
> --------------------------------------------------
> Solaris 10 (sparc)
> derbyall/derbynetmats/derbynetmats.fail:lang/wisconsin.java
> Solaris 8 (sparcN-2)
> derbyall/derbynetmats/derbynetmats.fail:lang/wisconsin.java
> Solaris 10, local zone (sparc_zone1)
> derbyall/derbynetmats/derbynetmats.fail:lang/wisconsin.java
> Solaris 10, local zone (sparc_zone3)
> derbynetclientmats/derbynetmats/derbynetmats.fail:lang/wisconsin.java
> Solaris 10, global zone (zones)
> derbynetmats/derbynetmats.fail:lang/wisconsin.java
> Java 5 (Sun's HotSpot VM, v1.5.0):
> ---------------------------------------------------------------
> Solaris 9 (sparcN-1) 
> derbyall/derbynetclientmats/derbynetmats.fail:lang/wisconsin.java
> Solaris 8 (sparcN-2)
> derbyall/derbynetmats/derbynetmats.fail:lang/wisconsin.java 
> See http://www.nabble.com/10.2.0.4-Test-results-p5485739.html for details.

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