db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-5105) NoSuchMethodError in upgrade tests (testTriggerBasic)
Date Sun, 13 Mar 2011 10:57:59 GMT

     [ 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.


If you experience this after soft upgrade from one of the affected version to or
later version and reverting back to the old version, use one of the following workarounds:

Workaround 1: Reboot the database using Derby 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:,
>            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;:
> 	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

View raw message