[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12424100 ] John H. Embretsen commented on DERBY-1564: ------------------------------------------
Preliminary test results: - I have not yet been able to reproduce the failure. I have tried running lang/wisconsin.java with Derby 10.2.0.4 on some of the machines where the test failed during the snapshot testing reported in http://www.nabble.com/10.2.0.4-Test-results-p5485739.html (jvm 1.5 or 1.6-b91, depending on platform). However, I still have some combinations to try (different platforms, running a suite instead of just the test, etc.). - I have not yet been successful with the approach suggested by Andreas. When I use the 10.2.0.4 derbyTesting.jar with the other 10.1.3.1 jars, I get a java.lang.ExceptionInInitializerError caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission derby.debug.false read) This happens when the server is started by the harness, so adding -DnoSecurityManager=true when starting the test does not help. Is there a way to turn off the Security Manager on the server without starting the server manually, or changing anything in the jar file? Some jvmflags, perhaps? - The approach suggested by Kathey shows varying results, depending on platform. I have run the tests in all frameworks, with JCC version 2.4. In my 10.1 vs. 10.2 comparison testing, all tests pass with heap sizes of 32 MB or default. All tests fail with heap size 12 MB. On sparc (Solaris 10), all tests failed with heap size of 16 MB. On a Solaris 10 x86 machine (that particular machine was not part of the original snapshot testing), tests often (but not always) fail with 16 MB heap size and Derby 10.2.0.4 in the DerbyNet and DerbyNetClient frameworks, but pass with Derby 10.1.3.1. - It should be noted that I don't think the wisconsin test is intended to run on such small JVMs. The app.properties file specifies a minimum of 32 MB. Besides, the test has changed between 10.1.3.1 and 10.2, so the 10.1 vs. 10.2 test results are not necessarily comparable, as Andreas has pointed out. - I may post more test results next week... > 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
