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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2011/03/08 16:11:59 UTC
[jira] Created: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
NoSuchMethodError in upgrade tests (testTriggerBasic)
-----------------------------------------------------
Key: DERBY-5105
URL: https://issues.apache.org/jira/browse/DERBY-5105
Project: Derby
Issue Type: Bug
Components: SQL
Affects Versions: 10.7.1.1, 10.8.0.0
Reporter: Knut Anders Hatlen
If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
Example from the nightly testing:
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-5105:
--------------------------------------
Attachment: disable.diff
I've checked in the attached patch (committed with revision 1081072) that disables the post soft upgrade phase of testTriggerBasic if the version we test suffers from DERBY-4835.
I don't think we need to check in jar files from head of 10.5 and 10.6 just to test this. If someone wants to set up their test environments to run upgrade tests against head of the release branches, it should be easy enough to do that by using the derbyTesting.oldVersionsPath to override the set of versions to test against, without any need to check in unreleased jar files in the repository.
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
> Attachments: disable.diff
>
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (DERBY-5105) NoSuchMethodError in
upgrade tests (testTriggerBasic)
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006169#comment-13006169 ]
Knut Anders Hatlen edited comment on DERBY-5105 at 3/13/11 10:59 AM:
---------------------------------------------------------------------
Resolving issue as "Won't Fix" now that the failing part of test has been disabled. The bug only affects downgrade to a specific set of versions, it doesn't fail against the latest sources in the branches for the affected versions, and workarounds exist.
Workarounds:
If you experience this after soft upgrade from one of the affected versions to 10.7.1.1 or later and reverting back to the old version, use one of the following workarounds:
Workaround 1: Reboot the database using Derby 10.7.1.1 or later. Simply connect to the database and then disconnect without doing any other operations. When reverting to the old version again, the triggers should work correctly.
Workaround 2: After reverting to the old version, drop and recreate the affected triggers.
was (Author: knutanders):
Resolving issue as "Won't Fix" now that the failing part of test has been disabled. The bug only affects downgrade to a specific set of versions, it doesn't fail against the latest sources in the branches for the affected versions, and workarounds exists.
Workarounds:
If you experience this after soft upgrade from one of the affected version to 10.7.1.1 or later version and reverting back to the old version, use one of the following workarounds:
Workaround 1: Reboot the database using Derby 10.7.1.1 or later. Simply connect to the database and then disconnect without doing any other operations. When reverting to the old version again, the triggers should work correctly.
Workaround 2: After reverting to the old version, drop and recreate the affected triggers.
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
> Attachments: disable.diff
>
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005346#comment-13005346 ]
Knut Anders Hatlen commented on DERBY-5105:
-------------------------------------------
The problem is not seen if the user uses head of the 10.5 branch. A fix in 10.8 might be to stop storing the SPS in soft upgrade, so that the incompatible plan isn't attempted used on 10.5. But it's probably not worth doing just for supporting downgrade from 10.8 to a couple of releases three branches back in time. Especially when the workaround seems to be as easy as rebooting the database once using 10.8 before going back to 10.5.x (alternatively, drop and recreate the trigger after moving back to 10.5).
I'm inclined to simply skip the post soft upgrade part of testTriggerBasic if the version we're testing against is in the range [10.5.0.0, 10.5.3.2). We could also make the test order explicit, to ensure that the tests that reboot the database run after testTriggerBasic and thereby work around the downgrade problem, but that may hide a regression in this area later, so I think the skipping sounds better. We may also want to skip the post soft upgrade phase of testTriggerBasic for 10.6.1.0, which is the only other released version that lacks a fix for DERBY-4835. It's not causing a problem currently, since the signatures of the ResultSetFactory methods haven't changed after 10.6, but we may see similar problems on that version too if the signatures are changed in a future version. I think...
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-5105.
---------------------------------------
Resolution: Won't Fix
Resolving issue as "Won't Fix" now that the failing part of test has been disabled. The bug only affects downgrade to a specific set of versions, it doesn't fail against the latest sources in the branches for the affected versions, and workarounds exists.
Workarounds:
If you experience this after soft upgrade from one of the affected version to 10.7.1.1 or later version and reverting back to the old version, use one of the following workarounds:
Workaround 1: Reboot the database using Derby 10.7.1.1 or later. Simply connect to the database and then disconnect without doing any other operations. When reverting to the old version again, the triggers should work correctly.
Workaround 2: After reverting to the old version, drop and recreate the affected triggers.
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
> Attachments: disable.diff
>
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005347#comment-13005347 ]
Knut Anders Hatlen commented on DERBY-5105:
-------------------------------------------
Oops... 10.6.1.0 isn't the only 10.6.x without a fix for DERBY-4835. It wasn't in 10.6.2.1 either. So to prevent this failure, and the reappearance the next time the signatures change, I suggest we skip that part of the test for 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0 and 10.6.2.1. Downgrade to any other version should work fine, as far as I understand.
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005208#comment-13005208 ]
Kathey Marsden commented on DERBY-5105:
---------------------------------------
Is this something that is fixable on trunk or would resolution require time travel back to 10.5.3.0. Is the core problem that DERBY-4835 can't be fixed on the old version, 10.5.3.0? If a users uses the latest from the 10.5 branch will they see this problem?
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003992#comment-13003992 ]
Knut Anders Hatlen commented on DERBY-5105:
-------------------------------------------
If you between step 2 and 3 just reboot the database using 10.7.1.1 or higher, step 3 won't fail. I suppose that's because rebooting in soft-upgrade mode using a version on which DERBY-4835 is fixed, will invalidate the SPS so that 10.5.3.0 will correctly recompile it.
This is also why the test passes on most platforms. testIndex and testCreateTable reboot the database, and since most platforms run those test cases after testTriggerBasic, the rebooting will hide this problem.
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003990#comment-13003990 ]
Knut Anders Hatlen commented on DERBY-5105:
-------------------------------------------
To reproduce outside of the upgrade tests, and without using Java 7 or phoneME, perform the following steps:
1) Using Derby 10.5.3.0, execute the following SQL statements:
CREATE TABLE Trigger_t1
(c1 INTEGER NOT NULL GENERATED ALWAYS
AS IDENTITY (START WITH 1, INCREMENT BY 1),
max_size INTEGER NOT NULL,
CONSTRAINT c1_pk PRIMARY KEY (c1));
CREATE TABLE Trigger_t2
(c1 INTEGER DEFAULT 0 NOT NULL);
CREATE TRIGGER gls_blt_trg
AFTER INSERT ON Trigger_t1 FOR EACH ROW MODE DB2SQL
INSERT INTO Trigger_t2(c1)
VALUES ( (select max(c1) from Trigger_t1));
INSERT INTO Trigger_t1(max_size) VALUES(20);
2) Connect to the same database using Derby 10.7.1.1 or Derby trunk, and execute the following SQL statement:
INSERT INTO Trigger_t1(max_size) VALUES(20);
3) Connect to the database again using Derby 10.5.3.0, and execute the INSERT statement again. You'll then see the NoSuchMethodError:
ij> INSERT INTO Trigger_t1(max_size) VALUES(20);
ERROR XJ001: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-5105) NoSuchMethodError in upgrade tests
(testTriggerBasic)
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005361#comment-13005361 ]
Kathey Marsden commented on DERBY-5105:
---------------------------------------
That sounds reasonable. To get some coverage on the 10.5 and 10.6 branches, I suppose we could check in a snapshot of the branch, but perhaps that would be too confusing. It would be nice to see a stand alone fixture for this case that is not dependent on fixture ordering for this case.
I think once the test issues are resolved this issue could be closed Won't fix with instructions about work arounds or maybe even dup it to DERBY-4835.
> NoSuchMethodError in upgrade tests (testTriggerBasic)
> -----------------------------------------------------
>
> Key: DERBY-5105
> URL: https://issues.apache.org/jira/browse/DERBY-5105
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Knut Anders Hatlen
>
> If the test case BasicSetup.testTriggerBasic runs after the test cases testCreateTable and testIndex, the upgrade test will fail with a NoSuchMethodError in the post soft upgrade phase when testing upgrade from 10.5.x.
> Example from the nightly testing:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1076682-suitesAll_diff.txt
> 2) testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)java.sql.SQLException: Java exception: 'org.apache.derby.iapi.sql.execute.ResultSetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/GeneratedMethod;IIZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: java.lang.NoSuchMethodError'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:82)
> It's seen occasionally on Java 7 and consistently on phoneME.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira