[
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
