[jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12433798 ] Øystein Grøvlen commented on DERBY-1691: The problem here is that output to stdout and stderr gets merge in different ways in different test runs. This problem can not be solved by just updating the master files! I plan to fix this by making sure all output goes to stdout. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.1.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: Øystein Grøvlen Fix For: 10.2.1.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12433805 ] Andreas Korneliussen commented on DERBY-1691: - Patch looks good. Got one conflict in DerbyNet.exclude, which I resolved. I will run some tests and commit. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.1.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: Øystein Grøvlen Fix For: 10.2.1.0 Attachments: derby-1651.diff With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12430605 ] Rick Hillegas commented on DERBY-1691: -- Ported DERBY-1691 (434245) to 10.2 branch at subversion revision 436921. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.1.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.1.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12430137 ] Andrew McIntyre commented on DERBY-1691: blobclob4BLOB excluded from running against JCC with revision 434245. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.1.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.1.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12429965 ] John H. Embretsen commented on DERBY-1691: -- With revision 433790, Andrew McIntyre tried to fix this issue by adding and modifying master files: r433790 | fuzzylogic | 2006-08-23 00:54:32 +0200 (Wed, 23 Aug 2006) | 3 lines Add some JCC and JDK version specific masters in the hopes of fixing the blobclob4BLOB test. Changed files: trunk/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNet/blobclob4BLOB.out (modified , text changed) trunk/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNet/jdk15/blobclob4BLOB.out (added) trunk/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNet/ver2.6/blobclob4BLOB.out (added) http://www.nabble.com/Re%3A-svn-commit%3A-r433790---in--db-derby-code-trunk-java-testing-org-apache-derbyTesting-functionTests-master-DerbyNet%3A-blobclob4BLOB.out-jdk15-blobclob4BLOB.out-ver2.6-blobclob4BLOB.out-t2149648.html Unfortunately, this effort was not successful: http://www.nabble.com/Regression-Test-Failure%21---TinderBox_Derby-433825---Sun-DBTG-t2150345.html This test should probably be excluded from the DerbyNet framework until we have a working solution. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.1.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.1.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428986 ] Øystein Grøvlen commented on DERBY-1691: David, the test is now failing with the same diff as two fixes ago. It seems like you have been toggling back and forth between two different master files that both creates problems. From what I can see from the diffs, the problem is that the sequence of output is not always the same. This can not be solved by switching from one sequence to another in the master file. One will have to fix the test so that the output sequence is deterministic. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.1.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.1.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428596 ] John H. Embretsen commented on DERBY-1691: -- This test is still failing in the Tinderbox runs, but because of the master file update in SVN 431663, the diff is different: * Diff file derbyall/derbynetmats/DerbyNet/jdbcapi/blobclob4BLOB.diff *** Start: blobclob4BLOB jdk1.5.0_04 DerbyNet derbynetmats:jdbcapi 2006-08-17 00:43:40 *** 474a475 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 476d476 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 782a783 java.lang.NegativeArraySizeException 784d784 java.lang.NegativeArraySizeException Test Failed. *** End: blobclob4BLOB jdk1.5.0_04 DerbyNet derbynetmats:jdbcapi 2006-08-17 00:44:12 *** I think simply changing the master file may not be the right solution in this case, but I have not looked at it enough to suggest an alternative yet. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428736 ] David Van Couvering commented on DERBY-1691: Sigh... I'll look at this. Really, it passed on my platform. Craig, this is the *last* time I'll commit a patch for you :) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 Is there a download site where one can get access to the 2.6 JCC driver? I think I asked this last spring and at the time there wasn't one available. It would be nice to be able to run JCC 2.6 tests myself occasionally. thanks, bryan
Re: Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
On 8/17/06, Bryan Pendleton [EMAIL PROTECTED] wrote: jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 Is there a download site where one can get access to the 2.6 JCC driver? I think I asked this last spring and at the time there wasn't one available. It would be nice to be able to run JCC 2.6 tests myself occasionally. The Cloudscape installer on the IBM Cloudscape website contains JCC 2.6. Click Trials and Demos at http://www.ibm.com/software/data/cloudscape/ The Java version is the smallest download, while the Windows and Linux versions also come with IBM JDK 1.4.2 for those platforms. andrew
Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
You can also get JCC separately (but it looks like it's version 2.4) by going to http://www14.software.ibm.com/webapp/download/search.jsp?go=yrs=cloudscape. Look for IBM DB2 JDBC Universal Driver in the list. Andrew McIntyre wrote: On 8/17/06, Bryan Pendleton [EMAIL PROTECTED] wrote: jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 Is there a download site where one can get access to the 2.6 JCC driver? I think I asked this last spring and at the time there wasn't one available. It would be nice to be able to run JCC 2.6 tests myself occasionally. The Cloudscape installer on the IBM Cloudscape website contains JCC 2.6. Click Trials and Demos at http://www.ibm.com/software/data/cloudscape/ The Java version is the smallest download, while the Windows and Linux versions also come with IBM JDK 1.4.2 for those platforms. andrew .
db2jcc jar files (was Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6)
Since failures in DerbyNet seem to be part of the overall regression failures that people hit, it would be great if the db2jcc jar files were just available rather than having to go through the process of registering and installing Cloudscape to get the jars. Any reason these can't be checked into tools/java, as long as they are not getting distributed in the release? Or are there legal constraints? David David Van Couvering (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428736 ] David Van Couvering commented on DERBY-1691: Sigh... I'll look at this. Really, it passed on my platform. Craig, this is the *last* time I'll commit a patch for you :) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 ***
Re: db2jcc jar files (was Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6)
David Van Couvering wrote: Since failures in DerbyNet seem to be part of the overall regression failures that people hit, it would be great if the db2jcc jar files were just available rather than having to go through the process of registering and installing Cloudscape to get the jars. Any reason these can't be checked into tools/java, as long as they are not getting distributed in the release? Or are there legal constraints? Software under one of the Category A licenses listed at http://www.apache.org/legal/3party.html may be checked into an ASF svn repo. I don't think these qualify. -jean David David Van Couvering (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428736 ] David Van Couvering commented on DERBY-1691: Sigh... I'll look at this. Really, it passed on my platform. Craig, this is the *last* time I'll commit a patch for you :) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 ***
[jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428831 ] David Van Couvering commented on DERBY-1691: Ok, I downloaded JCC 1.6 and tried again. I filtered out the strange obfuscated class path diffs using a sed file. It now passes with JCC 1.6. I don't feel obligated to get this to work on other versions of JCC. Checked in revision 432432. I'll check the next test run and see if this solves the problem. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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: db2jcc jar files (was Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6)
Jean T. Anderson wrote: David Van Couvering wrote: Since failures in DerbyNet seem to be part of the overall regression failures that people hit, it would be great if the db2jcc jar files were just available rather than having to go through the process of registering and installing Cloudscape to get the jars. Any reason these can't be checked into tools/java, as long as they are not getting distributed in the release? Or are there legal constraints? Software under one of the Category A licenses listed at http://www.apache.org/legal/3party.html may be checked into an ASF svn repo. I don't think these qualify. oh, wait, wait, not so fast I tell myself Category B also works -- we're talking about binaries. So anything that's Category A or B would be fine. -jean
Re: db2jcc jar files (was Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6)
Sigh... Could we post it on our Wiki? Jean T. Anderson wrote: David Van Couvering wrote: Since failures in DerbyNet seem to be part of the overall regression failures that people hit, it would be great if the db2jcc jar files were just available rather than having to go through the process of registering and installing Cloudscape to get the jars. Any reason these can't be checked into tools/java, as long as they are not getting distributed in the release? Or are there legal constraints? Software under one of the Category A licenses listed at http://www.apache.org/legal/3party.html may be checked into an ASF svn repo. I don't think these qualify. -jean David David Van Couvering (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428736 ] David Van Couvering commented on DERBY-1691: Sigh... I'll look at this. Really, it passed on my platform. Craig, this is the *last* time I'll commit a patch for you :) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 ***
Re: db2jcc jar files (was Re: [jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6)
David Van Couvering wrote: Sigh... Could we post it on our Wiki? I'm uncomfortable with that. I pinged legal-discuss@ a while ago re uploads to the Wiki and, based on their feedback, put up the http://wiki.apache.org/db-derby/UploadingCode page. One of them reminded me about the license header change and I see I need to update the wiki page. :-) -jean Jean T. Anderson wrote: David Van Couvering wrote: Since failures in DerbyNet seem to be part of the overall regression failures that people hit, it would be great if the db2jcc jar files were just available rather than having to go through the process of registering and installing Cloudscape to get the jars. Any reason these can't be checked into tools/java, as long as they are not getting distributed in the release? Or are there legal constraints? Software under one of the Category A licenses listed at http://www.apache.org/legal/3party.html may be checked into an ASF svn repo. I don't think these qualify. -jean David David Van Couvering (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428736 ] David Van Couvering commented on DERBY-1691: Sigh... I'll look at this. Really, it passed on my platform. Craig, this is the *last* time I'll commit a patch for you :) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 ***
[jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428209 ] Craig Russell commented on DERBY-1691: -- There is a tiny difference in the message text for: com.ibm.db2.jcc.c.SqlException com.ibm.db2.jcc.a.SqlException Is the difference something needs to be explained? Craig jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
I reran the tests and got the same diffs, so I applied the changes and committed. I suspect we have a version difference between the JCC drivers that I have been running and what is used in the regression tests. David Craig Russell (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12428209 ] Craig Russell commented on DERBY-1691: -- There is a tiny difference in the message text for: com.ibm.db2.jcc.c.SqlException com.ibm.db2.jcc.a.SqlException Is the difference something needs to be explained? Craig jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test, Regression Test Failure Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Assigned To: David Van Couvering Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 ***
[jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12427973 ] Rajesh Kartha commented on DERBY-1691: -- The failure was seen with the build - 10.2.1.0 beta - (430903), the beta candidate posted) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12427978 ] David Van Couvering commented on DERBY-1691: The problem is I don't get this diff on my machine. I am not even sure that the differences are.-- if you look at them, the text looks exactly the same. Guidance much appreciated. jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 -- Key: DERBY-1691 URL: http://issues.apache.org/jira/browse/DERBY-1691 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.2.0.0 Environment: Linux 2.6.9-5.ELsmp Sun jdk 1.5.0_07-b03 Reporter: Rajesh Kartha Fix For: 10.2.0.0 With JCC 2.6, the jdbcapi/blobclob4BLOB.java fails. The diff did not show anything alarming, so I am guessing it may be a master update. The test passed fine with DerbyClient *** Start: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:29:48 *** 466a467,474 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 468,475d475 EXPECTED SQLSTATE(22018): Invalid character string format for type INTEGER. end clobTest54 START: clobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.StringIndexOutOfBoundsException: String index out of range: -1 775a776,782 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 777,783d783 blobTest54 finished START: blobTest6 EXPECTED SQLSTATE(null): Invalid position 0 or length 5 EXPECTED SQLSTATE(null): Invalid position 1 or length -76 EXPECTED SQLSTATE(null): Invalid position 1 or length -1 EXPECTED SQLSTATE(null): Invalid position 0 or length 0 FAIL -- unexpected exception:java.lang.NegativeArraySizeException 789 del com.ibm.db2.jcc.c.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. 789a789 com.ibm.db2.jcc.a.SqlException: Operation 'CREATE TRIGGER' cannot be performed on object 'TESTBLOB' because there is an open ResultSet dependent on that object. Test Failed. *** End: blobclob4BLOB jdk1.5.0_06 DerbyNet derbynetmats:jdbcapi 2006-08-11 23:30:46 *** -- 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] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
David Van Couvering (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12427978 ] David Van Couvering commented on DERBY-1691: The problem is I don't get this diff on my machine. I am not even sure that the differences are.-- if you look at them, the text looks exactly the same. Guidance much appreciated. Did you try with a real diff utiltiy, rather than the simple one the test harness uses? diff $DM blobclob4BLOB.out were DM= the master folder. Dan.
