[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Kathey Marsden updated DERBY-1564:
----------------------------------
Priority: Critical (was: Major)
Raising this to critcial and Fix Version 10.2. I think we need to resolve
whether the increased memory usage for this test is 1) a regression 2)
Platform/JCC specific before we release 10.2. One good approach to verify
this would be to run the test with reduced memory heap. See
RegressionSearchAndDestroy hint in previous comment.
> 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
