[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12423858 ] Andreas Korneliussen commented on DERBY-1564: ---------------------------------------------
I think experimenting with different heap-sizes is slightly off-track, since all it may prove is that derby 10.2 may use more memory than derby 10.1 (then excluding the fact that the test has changed). This error was seen in a very specific environment: new VMs (JVM 1.5 and JVM 1.6), and on Sparc platform (real multi CPU) and in Solaris Zones environment (which will affect timing). This test has previously had timing issues. Would it be possible to run the test in the same environment as it failed using the derbyTesting.jar from 10.2, against Derby jar files from 10.1 ? If the error is reproduced, it indicates that this is not a regression, however still it may be a serious bug. --- The tests have been changed in DERBY-937. One change was to allow the optimizer to use as much time as it want in order to find the perfect query plan. The other change was to run compress on the tables. This happens before the test starts running the sql script which gives output. To me, this indicates, that the added compress may have played a part of the issue (since it did not give any output). > 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 > Priority: Critical > 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
