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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2009/09/22 08:48:16 UTC
[jira] Created: (DERBY-4384) testDynamicArgsMetaData has been
failing since Aug 24th on weme6.2 with NoSuchMethodError
testDynamicArgsMetaData has been failing since Aug 24th on weme6.2 with NoSuchMethodError
-----------------------------------------------------------------------------------------
Key: DERBY-4384
URL: https://issues.apache.org/jira/browse/DERBY-4384
Project: Derby
Issue Type: Bug
Components: Test
Affects Versions: 10.6.0.0
Environment: weme 6.2
Reporter: Mamta A. Satoor
testDynamicArgsMetaData has been failing on weme6.2 with following exception.
1) testDynamicArgsMetaData(org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest)java.lang.NoSuchMethodError: java/sql/PreparedStatement.getParameterMetaData()Ljava/sql/ParameterMetaData;
at org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest.testDynamicArgsMetaData(OffsetFetchNextTest.java:788)
at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:195)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
Kathey posted in her mail to Derby dev list that "I assume the failure was introduced by revision 807337 for DERBY-4208 (Parameters ? with OFFSET and/or FETCH) by Dag. That is the change that added the test on August 24."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4384) testDynamicArgsMetaData has been
failing since Aug 24th on weme6.2 with NoSuchMethodError
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759396#action_12759396 ]
Mamta A. Satoor commented on DERBY-4384:
----------------------------------------
Disabled the test fixture from running in JSR169 with revision 818730. Commit comments are as follows
Disabling the test fixture testDynamicArgsMetaData from running in JSR169 environment because it makes a call PreparedStatement.getParameterMetaData() which is unavailable in JSR169.
> testDynamicArgsMetaData has been failing since Aug 24th on weme6.2 with NoSuchMethodError
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-4384
> URL: https://issues.apache.org/jira/browse/DERBY-4384
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: weme 6.2
> Reporter: Mamta A. Satoor
> Fix For: 10.6.0.0
>
>
> testDynamicArgsMetaData has been failing on weme6.2 with following exception.
> 1) testDynamicArgsMetaData(org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest)java.lang.NoSuchMethodError: java/sql/PreparedStatement.getParameterMetaData()Ljava/sql/ParameterMetaData;
> at org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest.testDynamicArgsMetaData(OffsetFetchNextTest.java:788)
> at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:195)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> Kathey posted in her mail to Derby dev list that "I assume the failure was introduced by revision 807337 for DERBY-4208 (Parameters ? with OFFSET and/or FETCH) by Dag. That is the change that added the test on August 24."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-4384) testDynamicArgsMetaData has been
failing since Aug 24th on weme6.2 with NoSuchMethodError
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor resolved DERBY-4384.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
> testDynamicArgsMetaData has been failing since Aug 24th on weme6.2 with NoSuchMethodError
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-4384
> URL: https://issues.apache.org/jira/browse/DERBY-4384
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: weme 6.2
> Reporter: Mamta A. Satoor
> Fix For: 10.6.0.0
>
>
> testDynamicArgsMetaData has been failing on weme6.2 with following exception.
> 1) testDynamicArgsMetaData(org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest)java.lang.NoSuchMethodError: java/sql/PreparedStatement.getParameterMetaData()Ljava/sql/ParameterMetaData;
> at org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest.testDynamicArgsMetaData(OffsetFetchNextTest.java:788)
> at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:195)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> Kathey posted in her mail to Derby dev list that "I assume the failure was introduced by revision 807337 for DERBY-4208 (Parameters ? with OFFSET and/or FETCH) by Dag. That is the change that added the test on August 24."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4384) testDynamicArgsMetaData has been
failing since Aug 24th on weme6.2 with NoSuchMethodError
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760621#action_12760621 ]
Dag H. Wanvik commented on DERBY-4384:
--------------------------------------
Thanks for fixing this in my absence, Mamta. I was under the impression we ran our nightlies with JSR169 now, but it seems I am wrong. I'll check with Ole.
> testDynamicArgsMetaData has been failing since Aug 24th on weme6.2 with NoSuchMethodError
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-4384
> URL: https://issues.apache.org/jira/browse/DERBY-4384
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: weme 6.2
> Reporter: Mamta A. Satoor
> Fix For: 10.6.0.0
>
>
> testDynamicArgsMetaData has been failing on weme6.2 with following exception.
> 1) testDynamicArgsMetaData(org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest)java.lang.NoSuchMethodError: java/sql/PreparedStatement.getParameterMetaData()Ljava/sql/ParameterMetaData;
> at org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest.testDynamicArgsMetaData(OffsetFetchNextTest.java:788)
> at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:195)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> Kathey posted in her mail to Derby dev list that "I assume the failure was introduced by revision 807337 for DERBY-4208 (Parameters ? with OFFSET and/or FETCH) by Dag. That is the change that added the test on August 24."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.