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] Commented: (DERBY-1564) wisconsin.java test failed in DerbyNet or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Date Mon, 07 Aug 2006 09:20:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12426175 ] 
            
John H. Embretsen commented on DERBY-1564:
------------------------------------------

This was only seen on the combination of Solaris OS and Sparc processors during 10.2.0.4 snapshot
testing at Sun DBTG, and I have not seen the failure on any other platform (with default heap
sizes). However, I have been focusing on trying to reproduce the failures on the specific
platforms where the test failed instead of trying platforms where it did not fail, so I cannot
say with very high confidence that it will never happen on other platforms.

I have been able to reproduce the failure manually on some of the platforms, but only when
running suites. On some platforms I have only been able to reproduce it when running derbyall,
while on other platforms it has failed when running the derbynetmats or derbynetclientmats
suites. On some platforms it fails in both derbyall and (one or both of) the separate suites.
I have so far not been able to reproduce the failure by running the test by itself, which
makes it harder to debug. It also seems that it does not fail 100% of the time on some platforms.

I have been using 10.2.0.4 jars for the most part, because there has been some (unrelated)
noise surrounding the wisconsin test since the snapshot was made (DERBY-1609, DERBY-1625,
DERBY-1649). Also, once the patch for DERBY-1614 goes in, the test will run with different
(larger) heap sizes by default, which largely reduces the risk of us seeing this failure in
the near future.


> 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.0.0
>         Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework.
>            Reporter: Andreas Korneliussen
>             Fix For: 10.2.0.0
>
>         Attachments: 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