[
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
