[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12422784 ] Kathey Marsden commented on DERBY-1564: ---------------------------------------
RegressionSearchAndDestroy hint: The wisconsin.sql test in the past has been a canary in the mine for memory issues with Derby and Network Server, so it would be good to determine if this is a regression. Even if it doesn't run out of memory for you on your platform, a good thing to try is run with low memory on both 10.1 and 10.2 by setting the memory heap low e.g. -Djvmflags=-mx8M and comparing 10.1 and 10.2 behavior. > wisconsin.sql test failed in DerbyNet framework, 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 > Affects Versions: 10.2.0.0 > Environment: Solaris Sparc, Java 6, running in a Solaris Zone. > DerbyNet framework. > Reporter: Andreas Korneliussen > Attachments: wisconsin.tar.gz > > > The wisconsin test failed when running it in DerbyNet framework. No output in > the outfile. The DerbyNet.err file has one message: > Exception in thread "Thread-2" java.lang.OutOfMemoryError: Java heap space > The test was run against 10.2.0.4 snapshot release. -- 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
