[
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
