You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Andreas Korneliussen (JIRA)" <de...@db.apache.org> on 2006/07/21 17:23:19 UTC
[jira] Created: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
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
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
[jira] Commented: (DERBY-1564) wisconsin.java test failed in
DerbyNet or DerbyNetClient frameworks, VM for network server got
OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12428614 ]
John H. Embretsen commented on DERBY-1564:
------------------------------------------
Reply to Kathey's comment on Aug 10, 2006:
---------------------------------------------------------------------------------
Seems to me that both the wisconsin test and stress.multi cause a lot of noise for testers and developers, but that this is something we have to accept, since every once in a while they may uncover a real product defect. But I think too few people know enough about these test to understand what they are supposed to do, what they really do, why we have these instabilities, and how to get rid of them. For example, compressing the tables in wisconsin helped fix DERBY-937 on most platforms with 10.2, but it seems that it is not exactly clear why it helped. Having more tests that are testing memory consumption directly (such as derbyStress.java) would be nice, I agree.
Kathey wrote:
-------------------------
"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?"
Short answer:
-------------------------
Wisconsin should probably be running with at least 128 MB max heap size (which is the current setting). However, DERBY-1614 (which was partly and unintentionally caused by the fix for DERBY-1091) caused it to run with less memory (32 MB) for a while in trunk. Before the fix for DERBY-1091 was committed, the test was run with the jvm's defult heap size, which varies from platform to platform. This was not intentional either; it was intended to run with 128 MB max heap as specified in wisconsin_app.properties.
Long answer:
-------------------------
Well, I think one reason for all the confusion is that assumptions were made early on (about default heap sizes), that are no longer valid in general. Here's the comment from wisconsin_app.properties, which has been there since the test was contributed to Apache in 2004:
# flags specific to this test: it runs out of memory on jdk118 sometimes
# so give the JVM more memory always:
jvmflags=-ms32M -mx128M
(The format of the jvmflags has been changed in 10.2 and trunk. The values are still the same).
This means that the default max heap size on jdk118 was considerably less than 128 MB, and that someone determined that the test needed this much memory to be able to run successfully. I don't know if this setting ever worked before the test and the harness was open-sourced, but it certainly does not work in 10.1, and it did not work in trunk/10.2 until the patch for DERBY-1614 was committed.
Currently the default max heap size of most newer JVMs on reasonably new machines is equal to or larger than the setting that is specified for wisconsin. This means that wisconsin.java (trunk/10.2. since SVN rev 429550) on some platforms actually runs with a lower heap size than other tests. But that's no big deal - yet.
That is also the reason why the patch for DERBY-1614 removed the harness code that set heap sizes for the Network Server by default. The harness default was a max heap size of 32 MB (the reasoning was that the Network Server needs more memory than the JVM's default), but that value was set a long time ago (as Myrna explained in a comment to DERBY-1614), and did not make sense anymore.
I don't know if DERBY-1315 is related, since I don't know enough about what the wisconsin test actually does.
> 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: port-wisconsin-from-10.2.0.4-to-10.1_v1.stat, port-wisconsin-from-10.2.0.4-to-10.1_v1.zip, 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
[jira] Closed: (DERBY-1564) wisconsin.java test failed in DerbyNet
or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Andreas Korneliussen closed DERBY-1564.
---------------------------------------
Thanks for resolving this issue, I agree it can be closed.
> 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.1.0
> Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework.
> Reporter: Andreas Korneliussen
> Assigned To: John H. Embretsen
> Fix For: 10.2.1.0
>
> Attachments: port-wisconsin-from-10.2.0.4-to-10.1_v1.stat, port-wisconsin-from-10.2.0.4-to-10.1_v1.zip, 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
[jira] Commented: (DERBY-1564) wisconsin.sql test failed in
DerbyNet framework, VM for network server got OutOfMemoryError
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1564) wisconsin.java test failed in DerbyNet
or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
John H. Embretsen updated DERBY-1564:
-------------------------------------
Fix Version/s: (was: 10.2.1.0)
Derby Info: (was: [Patch Available])
The failures described in this issue were mainly triggered by a bug in the test harness which has been fixed in 10.2 and trunk. I am wondering if we should close this issue and open a new one for the porting of the 10.2.0.4 wisconsin test to the 10.1 branch (I have a new patch ready for that), and possibly one for running the wisconsin test with smallish Java heaps (< 32 MB).
Any thoughts or objections?
Not sure what the fix version should be here, if any, so unsetting it for now...
> 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.1.0
> Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework.
> Reporter: Andreas Korneliussen
> Assigned To: John H. Embretsen
> Attachments: port-wisconsin-from-10.2.0.4-to-10.1_v1.stat, port-wisconsin-from-10.2.0.4-to-10.1_v1.zip, 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
[jira] Commented: (DERBY-1564) wisconsin.sql test failed in
DerbyNet framework, VM for network server got OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1564) wisconsin.java test failed in DerbyNet
or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Andrew McIntyre updated DERBY-1564:
-----------------------------------
Derby Info: [Patch Available]
Setting patch available for John's port-wisconsin-from-10.2.0.4-to-10.1_v1.zip patch.
> 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.1.0
> Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework.
> Reporter: Andreas Korneliussen
> Fix For: 10.2.1.0
>
> Attachments: port-wisconsin-from-10.2.0.4-to-10.1_v1.stat, port-wisconsin-from-10.2.0.4-to-10.1_v1.zip, 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
[jira] Updated: (DERBY-1564) wisconsin.java test failed in DerbyNet
or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
John H. Embretsen updated DERBY-1564:
-------------------------------------
Attachment: port-wisconsin-from-10.2.0.4-to-10.1_v1.zip
port-wisconsin-from-10.2.0.4-to-10.1_v1.stat
Attatching patch ('port-wisconsin-from-10.2.0.4-to-10.1_v1.zip') and output from 'svn stat -q' ('port-wisconsin-from-10.2.0.4-to-10.1_v1.stat') which attempts to port the wisconsin test from 10.2.0.4 (SVN revision 423199) to the current head of the 10.1 branch. The patch is zipped because removal of two master files makes it 3.3 MB unzipped.
NOTE:
I had one build problem when applying this patch:
wisc_setup.sql does not appear in /classes/org/apache/derbyTesting/functionTests/tests/lang/wisc_setup.sql (and thus not in derbyTesting.jar) automatically by running 'ant all', and I have no idea why not.
My quick fix was to manually copy wisc_setup.sql from its source location under java/ to its build location under classes/ before building the jars, but after running 'ant all'.
Summary of changes:
- renames the test from lang/wisconsin.sql to lang/wisconsin.java (DERBY-398)
- adds wisc_setup.sql support file (DERBY-398)
- removes framework-specific master files (for DerbyNet and DerbyNetClient) (DERBY-822)
- runs compress on tables before retreiving runtimestatistics (DERBY-937)
- adds property derby.optimizer.noTimeout=true to wisconsin_derby.properties (DERBY-413/DERBY-937)
I have run the lang/wisconsin.java test with this patch applied to 10.1 using Sun's JVMs 1.4.2 and 1.5.0 in all three frameworks on a Solaris 10 x86 machine and a Solaris 9 sparc machine, no failures.
However, since the rest of DERBY-822 is not in the 10.1 branch (but changes to seding and output from this test is included in this patch since it was included in 10.2.0.4), we might expect diffs on some platforms (?).
So, the changes related to DERBY-822 may have to be removed, but I'm uploading the patch anyway, since I don't have time to dive deeper into this right now (not this week, at least), and I have not seen any diffs so far.
Changes committed to trunk/10.2 after 10.2.0.4 are not included, since then the IJ implementation would have to change too (DERBY-1609).
Feel free to play with this patch. I may be able to upload a new patch if I get a solution for the build problem and if someone can confirm that the 822-changes may cause problems.
> 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: port-wisconsin-from-10.2.0.4-to-10.1_v1.stat, port-wisconsin-from-10.2.0.4-to-10.1_v1.zip, 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
[jira] Commented: (DERBY-1564) wisconsin.java test failed in
DerbyNet or DerbyNetClient frameworks, VM for network server got
OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12426175 ]
John H. Embretsen commented on DERBY-1564:
------------------------------------------
This was only seen on the combination of Solaris OS and Sparc processors during 10.2.0.4 snapshot testing at Sun DBTG, and I have not seen the failure on any other platform (with default heap sizes). However, I have been focusing on trying to reproduce the failures on the specific platforms where the test failed instead of trying platforms where it did not fail, so I cannot say with very high confidence that it will never happen on other platforms.
I have been able to reproduce the failure manually on some of the platforms, but only when running suites. On some platforms I have only been able to reproduce it when running derbyall, while on other platforms it has failed when running the derbynetmats or derbynetclientmats suites. On some platforms it fails in both derbyall and (one or both of) the separate suites. I have so far not been able to reproduce the failure by running the test by itself, which makes it harder to debug. It also seems that it does not fail 100% of the time on some platforms.
I have been using 10.2.0.4 jars for the most part, because there has been some (unrelated) noise surrounding the wisconsin test since the snapshot was made (DERBY-1609, DERBY-1625, DERBY-1649). Also, once the patch for DERBY-1614 goes in, the test will run with different (larger) heap sizes by default, which largely reduces the risk of us seeing this failure in the near future.
> 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
[jira] Commented: (DERBY-1564) wisconsin.sql test failed in
DerbyNet framework, VM for network server got OutOfMemoryError
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1564) wisconsin.java test failed in DerbyNet
or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Rick Hillegas updated DERBY-1564:
---------------------------------
Urgency: Normal (was: Urgent)
Thanks, John, for all of your hard work reproducing this problem on 10.1.3. Based on John's experiments, it appears that this behavior is not a regression introduced by 10.2 changes. I do not see any evidence of a product defect here. Instead, this looks like an artifact of changes to the testing environment. I am downgrading the urgency of this issue to Normal.
> 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
[jira] Commented: (DERBY-1564) wisconsin.java test failed in
DerbyNet or DerbyNetClient frameworks, VM for network server got
OutOfMemoryError
Posted by "Rajesh Kartha (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12426119 ]
Rajesh Kartha commented on DERBY-1564:
--------------------------------------
Seems the failure is happening only on Solaris (?). I tried the test with different jdks (Sun jdk 1.5, 1.6, IBM 1.4.2, 1.5) on Windows and Linux - RHEL 4.0 (Sun jdk 1.6 tests in progress) and was not able to reproduce this OOM error. The only failure I saw was DERBY-1649.
> 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
[jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Rick Hillegas updated DERBY-1564:
---------------------------------
Urgency: Urgent
Bumping urgency.
> 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
[jira] Commented: (DERBY-1564) wisconsin.sql test failed in
DerbyNet framework, VM for network server got OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12423846 ]
John H. Embretsen commented on DERBY-1564:
------------------------------------------
In the DerbyNet (and DerbyNetClient) framework the test harness spawns two new JVMs when running the lang/wisconsin.java test. One JVM is the Network Server JVM, and the other is the wisconsin test itself. It seems to me that the failure reported in this Jira-issue is caused by an OutOfMemoryError in the Network Server JVM, since the error is reported in the DerbyNet.err file only.
Hence, regression testers need to be aware of which heap size values actually has any effect on both JVMs when using the jvmflags property. Because of the complexity of the test harness, understanding this is not necessarily a trivial task, especially since the jvmflags property has a different effect in version 10.1.x.x vs. version 10.2.x.x.
Kathey recommended in a previous comment to run the test with reduced heap sizes, and compare results for 10.1 and 10.2. I have a few observations/recommendations in that regard, based on test runs with the Sun 1.5 JVM (using "jmap -heap <jvmid>" to get the actual max size of the JVM heap) and Derby versions 10.1.3.1 and 10.2.0.4:
10.1.3.1 testing:
---------------------------
Test name: lang/wisconsin.sql
Example heap size: 12 MB
- Use -Djvmflags="-ms12m -mx12m" (including quotes) (12M also works; these values are case insensitive).
- By using -Djvmflags=-mx12m, the Network Server process fails ("Incompatible initial and maximum heap sizes specified") since the harness automatically adds an -ms16777216 (initial heap size 16 MB), which is higher than the max heap size of 12 MB. Hence, using -mx only in jvmflags works only if the value of -mx is 16m or larger.
- By using -Djvmflags="-Xms12 -Xmx12m", the harness automatically adds "- ms16777216 -mx33554432" (excluding quotes) when starting the server JVM. These options are added _after_ the -Xms and -Xmx options , thus overriding the 12 MB values so that the network server will have a max heap size of 32 MB instead of 12 MB.
- Default heap size on my machine seems to be 64 MB for both JVMs. I don't know why the wisconsin_app.properties jvmflags (-ms32M -mx128M) are not used.
10.2.0.4 testing:
---------------------------
Test name: lang/wisconsin.java
Example heap size: 12 MB
- Use -Djvmflags=-Xms12m^-Xmx12m
The harness adds "-ms32M -mx128M" (from wisconsin_app.properties) automatically to the server JVM command, but puts it _before_ the jvmflags from the command line. Using both -Xms and -Xmx ensures that the values from wisconsin_app.properties are overridden, probably thanks to DERBY-1091.
- By using -Djvmflags=-Xmx12m, the "Incompatible initial and maximum heap sizes specified" problem from above reappears, since the max value of 12 MB is smaller than the initial value of 32 MB.
- By using -Djvmflags="-ms12m -mx12m", the server JVM heap size settings from the command line are overridden by the settings set by the test harness (a test harness bug?). The resulting java command line flags for the server JVM is: "java -ms32M -mx128M -ms12m -mx12m -ms16777216 -mx33554432", and the last value is used, which for max heap size is 33554432, which is 32 MB. Hence, the test may pass when it would have failed with correct jvm flags.
- It seems like the wisconsin_app.properties jvmflags values are overridden by the above mentioned server flags (-ms16777216 -mx33554432) when running the 10.2 version of the test without specifying heap size on the command line.
I got the flags passed on by the test harness by adding -Dverbose=true when starting the test via RunTest.
I hope this is useful when/if someone decides to start following the testing approach suggested by Kathey. I will run some tests myself, and will post the results here (or I will create a wiki page), presumably tomorrow, so that we may know more about what's going on.
Please yell if you think I have made any errors regarding the test harness and its jvmflags property, or drawn any wrong conclusions.
> 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
[jira] Resolved: (DERBY-1564) wisconsin.java test failed in
DerbyNet or DerbyNetClient frameworks, VM for network server got
OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
John H. Embretsen resolved DERBY-1564.
--------------------------------------
Fix Version/s: 10.2.1.0
Resolution: Fixed
The lang/wisconsin.java test has not failed with this error in regular regression testing since the 10.2.0.4 snapshot. The fix for DERBY-1614 is the reason for this. Hence, I am resolving this issue as fixed (not sure what the fix version should be).
What remains from previous comments is basically to port the wisconsin test from 10.2.0.4 to the 10.1 branch. This is being tracked by DERBY-1872.
Running the wisconsin test (even more) with low memory settings has also been proposed. I have no plans to continue this kind of testing in the near future. Here is a summary of my results:
* lang/wisconsin.java is quite unstable on most platforms when max heap size is smaller than 32 MB. Getting OutOfMemoryErrors with both trunk and 10.1.3.1, all frameworks (but I've been focusing mostly on Client/Server testing).
* lang/wisconsin.java, 32 MB max heap size, DerbyNet and DerbyNetClient frameworks:
* trunk: fails about 4 out of 10 times (may vary between OS, hardware, etc.), usually with an OutOfMemoryError (Java heap space).
* 10.1.3.1 with backported wisconsin test: ~ same as trunk, test is unstable with such small heap.
* 10.1.3.1: Passes most of the time.
* lang/wisconsin.java, 64 MB max heap size, all frameworks:
* No failures seen, both trunk and 10.1.3.1
I suggest we close this issue, and report any further testing with low memory settings as comments to DERBY-1568 ("run derbyall with low memory configuration for 10.2"), or create a new (sub)task for that specific purpose.
> 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.1.0
> Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework.
> Reporter: Andreas Korneliussen
> Assigned To: John H. Embretsen
> Fix For: 10.2.1.0
>
> Attachments: port-wisconsin-from-10.2.0.4-to-10.1_v1.stat, port-wisconsin-from-10.2.0.4-to-10.1_v1.zip, 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
Re: [jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
Posted by Kathey Marsden <km...@sbcglobal.net>.
Rick Hillegas wrote:
> I don't have strong religion about this. It's not clear whether this
> problem is an artifact of the testing environment or is a serious
> Derby bug. I have marked the issue as Urgent, which means that for
> 10.2 we intend to investigate this issue and fix the underlying bug if
> there turns out to be one.
>
Sounds resonable.
Re: [jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
Posted by Rick Hillegas <Ri...@Sun.COM>.
I don't have strong religion about this. It's not clear whether this
problem is an artifact of the testing environment or is a serious Derby
bug. I have marked the issue as Urgent, which means that for 10.2 we
intend to investigate this issue and fix the underlying bug if there
turns out to be one.
Regards,
-Rick
Kathey Marsden wrote:
> Rick Hillegas (JIRA) wrote:
>
>> [ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
>>
>> Rick Hillegas updated DERBY-1564:
>> ---------------------------------
>>
>> Priority: Major (was: Critical)
>>
>>
>>
> Since this test runs out of memory, does it not qualify as:
>
> Critical
> Crashes, loss of data, severe memory leak.
>
>
Re: [jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
Posted by Kathey Marsden <km...@sbcglobal.net>.
Rick Hillegas (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
>
>Rick Hillegas updated DERBY-1564:
>---------------------------------
>
> Priority: Major (was: Critical)
>
>
>
Since this test runs out of memory, does it not qualify as:
Critical
Crashes, loss of data, severe memory leak.
[jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Rick Hillegas updated DERBY-1564:
---------------------------------
Priority: Major (was: Critical)
> 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
[jira] Commented: (DERBY-1564) wisconsin.sql test failed in
DerbyNet framework, VM for network server got OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12424552 ]
John H. Embretsen commented on DERBY-1564:
------------------------------------------
Due to DERBY-1614 this test was most likely run with "too small" max heap size in the DerbyNet and DerbyNetClient frameworks during 10.2.0.4 snapshot testing.
This is indicated by the following process:
I used the following command to start the test:
$ java -Dverbose=true -Dframework=DerbyNet org.apache.derbyTesting.functionTests.harness.RunTest lang/wisconsin.java
With the 10.2.0.4 snapshot jars (as well as SVN revision 420048 and later), "jmap -heap <NetworkServerControl's vmid>" reveals that the max heap size is 32 MB. The heap flags set by the test harness were:
-ms32M -mx128M -ms16777216 -mx33554432
With SVN revision 420047 and earlier, jmap reports the maximum server heap size as 64 MB. The test harness did not seem to set any heap size flags. However, according to wisconsin_app.properties, the max heap size should be 128 MB. The jvmflags property from wisconsin_app.properties was probably not used because of the bug described in DERBY-1091 (?). A patch for DERBY-1091 was committed with SVN rev 420048. 64 MB is the default max heap size on my machine (with jdk 1.5).
The conclusion is that prior to SVN rev 420048 this test was (as far as I can tell) run with the default heap sizes of the test machine.
With SVN rev 420048 and later, this test has been run with a max heap size of 32 MB (server JVM). The 10.2.0.4 snapshot is SVN rev 423199.
I cannot (yet) tell for sure if this is the reason why the test failed on some platforms during the snapshot testing. There are too many variables in play here....
> 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
[jira] Commented: (DERBY-1564) wisconsin.sql test failed in
DerbyNet framework, VM for network server got OutOfMemoryError
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12422684 ]
Andreas Korneliussen commented on DERBY-1564:
---------------------------------------------
Do note that that there was not output in the outfile, and the diff file is therefore the entire master file.
Below is some output from the report file, which indicates the test ran for more than 1 hour before failing:
********* Diff file derbyall/derbynetmats/DerbyNet/derbynetmats/wisconsin.diff
*** Start: wisconsin jdk1.6.0-rc DerbyNet derbynetmats:derbynetmats 2006-07-19 16:46:20 ***
0 del
< ij> -- This test is an adaptation of the Wisconsin benchmark, as documented in
< ----- The Benchmark Handbook, Second Edition (edited by Jim Gray). The structure
... <SNIP>
< 0 rows inserted/updated/deleted
< ij>
Test Failed.
*** End: wisconsin jdk1.6.0-rc DerbyNet derbynetmats:derbynetmats 2006-07-19 17:49:18 ***
> 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
[jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Andreas Korneliussen updated DERBY-1564:
----------------------------------------
Attachment: wisconsin.tar.gz
Attaching log from test (wisconsin.tar.gz)
> 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
[jira] Commented: (DERBY-1564) wisconsin.java test failed in
DerbyNet or DerbyNetClient frameworks, VM for network server got
OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12426228 ]
John H. Embretsen commented on DERBY-1564:
------------------------------------------
I have spent much of the past few days trying to reproduce this failure and to get to know more about whether this is a regression or not. My conclusion so far is that this is *not* a regression. For details, read on...
In order to compare Derby 10.1.3.1 to Derby 10.2.0.4 as fairly as possible, I had to take a few extra steps:
* I ported the lang/wisconsin.java test from 10.2.0.4 (i.e., SVN revision 423199 of trunk) to 10.1.3.1 (i.e. SVN revision 417277 of the 10.1 branch). This was not entirely a trivial task, but I got it working. I did this because the test had changed so much between 10.1.x and 10.2.0.4 that results from the two versions were not directly comparable (see previous comment from Andreas). Besides, simply using the 10.2.0.4 derbyTesting.jar against 10.1.3.1 jars does not work.
* I chose one of the platforms where it failed on JDK 1.5 during the 10.2.0.4 snapshot testing. This was because the 10.1 test harness does not support jdk 1.6. So I used the sparcN-1 platform (the exact same machine) for comparison testing.
* Due to DERBY-1091, the wisconsin test run via the 10.1.x test harness runs with the JVM's default heap sizes. On the sparcN-1 platform, the default max heap size is 512 MB with JDK 1.5. Due to DERBY-1614, the wisconsin test in 10.2.0.4 runs with a max heap size of 32 MB (both the test and the Network Server). It is obvious that it would not be fair to compare the two versions directly. By adding -Djvmflags="-ms16m -mx32m" to the RunSuite command when running against the 10.1.3.1 jars, things looked much more fair. jmap reported equal max heap sizes for the two versions when I was checking while the suites were running.
So, with the 10.2.0.4 wisconsin test in the 10.1.3.1 derbyTesting.jar, and with the rest of the 10.1.3.1 jars in the classpath, I was able to reproduce the failure (i.e. OutOfMemoryError: Java heap space in the server VM) in both derbyall/derbynetclientmats and derbynetclientmats only, on that particular platform. I was also able to reproduce the original failure, using 10.2.0.4 jars only.
I am going to do some more testing later using single test runs via scripts, and intend to report my findings here.
> 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
[jira] Updated: (DERBY-1564) wisconsin.java test failed in DerbyNet
or DerbyNetClient frameworks, VM for network server got OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
John H. Embretsen updated DERBY-1564:
-------------------------------------
Summary: wisconsin.java test failed in DerbyNet or DerbyNetClient frameworks, VM for network server got OutOfMemoryError (was: wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError)
Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework. (was: Solaris Sparc, Java 6, running in a Solaris Zone. DerbyNet framework.)
Component/s: Regression Test Failure
Description:
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.
was:
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.
Modified Summary, Environment and Description so that they reflect the situation more accurately. Added component Regression Test Failure.
> 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
[jira] Commented: (DERBY-1564) wisconsin.java test failed in
DerbyNet or DerbyNetClient frameworks, VM for network server got
OutOfMemoryError
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Assigned: (DERBY-1564) wisconsin.java test failed in
DerbyNet or DerbyNetClient frameworks, VM for network server got
OutOfMemoryError
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
John H. Embretsen reassigned DERBY-1564:
----------------------------------------
Assignee: John H. Embretsen
> 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.1.0
> Environment: Solaris Sparc, Java 5 or 6, DerbyNet or DerbyNetClient framework.
> Reporter: Andreas Korneliussen
> Assigned To: John H. Embretsen
> Fix For: 10.2.1.0
>
> Attachments: port-wisconsin-from-10.2.0.4-to-10.1_v1.stat, port-wisconsin-from-10.2.0.4-to-10.1_v1.zip, 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
[jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet
framework, VM for network server got OutOfMemoryError
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Rick Hillegas updated DERBY-1564:
---------------------------------
Fix Version/s: 10.2.0.0
Assigning this to 10.2.
> 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
> Fix For: 10.2.0.0
>
> 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