[jira] Commented: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ 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

[jira] Commented: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ 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

[jira] Commented: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ 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

[jira] Commented: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ 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

[jira] Commented: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ 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