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 14:26:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12426228 ] 
            
John H. Embretsen commented on DERBY-1564:
------------------------------------------

I have spent much of the past few days trying to reproduce this failure and to get to know
more about whether this is a regression or not. My conclusion so far is that this is *not*
a regression. For details, read on...

In order to compare Derby 10.1.3.1 to Derby 10.2.0.4 as fairly as possible, I had to take
a few extra steps:

* I ported the lang/wisconsin.java test from 10.2.0.4 (i.e., SVN revision 423199 of trunk)
to 10.1.3.1 (i.e. SVN revision 417277 of the 10.1 branch). This was not entirely a trivial
task, but I got it working. I did this because the test had changed so much between 10.1.x
and 10.2.0.4 that results from the two versions were not directly comparable (see previous
comment from Andreas). Besides, simply using the 10.2.0.4 derbyTesting.jar against 10.1.3.1
jars does not work.

* I chose one of the platforms where it failed on JDK 1.5 during the 10.2.0.4 snapshot testing.
This was because the 10.1 test harness does not support jdk 1.6. So I used the sparcN-1 platform
(the exact same machine) for comparison testing.

* Due to DERBY-1091, the wisconsin test run via the 10.1.x test harness runs with the JVM's
default heap sizes. On the sparcN-1 platform, the default max heap size is 512 MB with JDK
1.5. Due to DERBY-1614, the wisconsin test in 10.2.0.4 runs with a max heap size of 32 MB
(both the test and the Network Server). It is obvious that it would not be fair to compare
the two versions directly. By adding -Djvmflags="-ms16m -mx32m" to the RunSuite command when
running against the 10.1.3.1 jars, things looked much more fair. jmap reported equal max heap
sizes for the two versions when I was checking while the suites were running.

So, with the 10.2.0.4 wisconsin test in the 10.1.3.1 derbyTesting.jar, and with the rest of
the 10.1.3.1 jars in the classpath, I was able to reproduce the failure (i.e. OutOfMemoryError:
Java heap space in the server VM) in both derbyall/derbynetclientmats and derbynetclientmats
only, on that particular platform. I was also able to reproduce the original failure, using
10.2.0.4 jars only.

I am going to do some more testing later using single test runs via scripts, and intend to
report my findings here.


> 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