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] Resolved: (DERBY-1564) wisconsin.java test failed in DerbyNet or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Date Thu, 21 Sep 2006 09:20:24 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]

John H. Embretsen resolved DERBY-1564.

    Fix Version/s:
       Resolution: Fixed

The lang/wisconsin.java test has not failed with this error in regular regression testing
since the snapshot. The fix for DERBY-1614 is the reason for this. Hence, I am resolving
this issue as fixed (not sure what the fix version should be).

What remains from previous comments is basically to port the wisconsin test from
to the 10.1 branch. This is being tracked by DERBY-1872.

Running the wisconsin test (even more) with low memory settings has also been proposed. I
have no plans to continue this kind of testing in the near future. Here is a summary of my

* lang/wisconsin.java is quite unstable on most platforms when max heap size is smaller than
32 MB. Getting OutOfMemoryErrors with both trunk and, all frameworks (but I've been
focusing mostly on Client/Server testing).

* lang/wisconsin.java, 32 MB max heap size, DerbyNet and DerbyNetClient frameworks:
    * trunk: fails about 4 out of 10 times (may vary between OS, hardware, etc.), usually
with an OutOfMemoryError (Java heap space).
    * with backported wisconsin test: ~ same as trunk, test is unstable with such
small heap.
    * Passes most of the time.

* lang/wisconsin.java, 64 MB max heap size, all frameworks:
    * No failures seen, both trunk and

I suggest we close this issue, and report any further testing with low memory settings as
comments to DERBY-1568 ("run derbyall with low memory configuration for 10.2"), or create
a new (sub)task for that specific purpose.

> 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:
>         Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework.
>            Reporter: Andreas Korneliussen
>         Assigned To: John H. Embretsen
>             Fix For:
>         Attachments: port-wisconsin-from-, port-wisconsin-from-,
> The wisconsin test failed on some Solaris (sparc) platforms during testing of the
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
> 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/ 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


View raw message