Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <19335863.1155260774304.JavaMail.jira@brutus>
Date: Thu, 10 Aug 2006 18:46:14 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1564) wisconsin.java test failed in
 DerbyNet or DerbyNetClient frameworks, VM for network server got
 OutOfMemoryError
In-Reply-To: <20757765.1153495399117.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12427386 ] 
            
Kathey Marsden commented on DERBY-1564:
---------------------------------------

Thanks John for investigating this issue.  If you have the wisconsin.java test ported to 10.1 and have a patch, I will commit.  It will be good to have for comparison.

I hope this won't cause you to lose faith in my  favorite memory sensitive test.  It has exposed important product issues in the past, and even here it detected subtle changes in  the test harness memory configuration.   I wonder too if  DERBY-1315 is at play here too.

It would be good to have tests targetted just for monitoring memory consumption that are easier to debug. For now stress.multi and wisconsin are still my friends.

One thing I am not clear on is that it sounds like the test harness change (DERBY-1091) that causes this test to run with less memory was intentional, but should wisconsin be running with  the lower memory configuration?  


> 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