There may be such problems, that's why this is a developer task. The purpose is to clear or document the problems.
The array size issue should be traced and fixed. Please specify -Dhsqldb.tracesystemout=true and/or -Dhsqldb.trace=true when running the tests to ge a better message. Fred ----- Original Message ----- From: "Carfield Yim" <[EMAIL PROTECTED]> To: <hsqldb-developers@lists.sourceforge.net> Sent: 07 March 2005 11:04 Subject: Re: [Hsqldb-developers] Fwd: Small developer tasks for 1.8.0 On Mon, 7 Mar 2005 10:14:34 -0000, fredt <[EMAIL PROTECTED]> wrote: > Hi Carfiled, > > The build process has changed over different versions. We cannot change it > as you suggest, as the issue is not just the use of collections and io > stuff. The primary issue that requires different JDK's is the changes in > java.sql interfaces between different JDK releases. > Really not possible? May be it is true as I don't really examine the code. However, if this really the case, may be better to having difference branch rather than keep everything in single branch with preprocessor. May be you already tried and have problem of this approach, just my personaly opinions. > For building for 1.1 with 1.3, you do not use switchtojdk11. The current > version of readmebuild.txt has the instructions as follows: > > ant switchtojava1target > > The jars compiled after this switch will run under JRE 1.3 too, but they > use > some deprecated JDK 1.1 methods. > > To switch back to non-deprecated code, use: > > ant switchoffjava1target > OK, the corrected ant target sequence is ant switchtojava1target ant jarmain I have encounter problem of running "ant jar" then try "ant jarmain", I can't find it at readmebuild.txt as well as the webpage, do you think it worth to document? Or again I miss it somewhere? Ok , now I can run my application with hsql compile in 1.1. As I mainly use hsql because it run my unittest very quick, so now I running all my testcase using hsql 1.1, the first 129 test are ok, and all the rest of testcase fail with the following exception, this may be jvm limitations array size (array size is byte? sound strange, but that what I can tell). However, my testcase have close the connection in teardown() method. So may be hsql can put new connect in the server to the array with closed connection? java.lang.RuntimeException: java.sql.SQLException: Connection is broken: Requested array size exceeds VM limit at com.netdimen.jdbc.core.JdbcTemplate.updateInternal(JdbcTemplate.java:45) at com.netdimen.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:62) at com.netdimen.core.IDManager.advanceSequences(IDManager.java:252) at com.netdimen.core.IDManager.<init>(IDManager.java:197) at com.netdimen.core.IDManager.<init>(IDManager.java:236) at com.netdimen.unittest.DatabaseTestCase.testContext(DatabaseTestCase.java:116) at com.netdimen.unittest.DatabaseTestCase.runBare(DatabaseTestCase.java:102) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:421) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:305) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:186) Caused by: java.sql.SQLException: Connection is broken: Requested array size exceeds VM limit at org.hsqldb.jdbc.jdbcUtil.sqlException(Unknown Source) at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source) at com.netdimen.jdbc.core.JdbcTemplate.updateInternal(JdbcTemplate.java:36) ... 19 more ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ hsqldb-developers mailing list hsqldb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hsqldb-developers ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ hsqldb-developers mailing list hsqldb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
