[ 
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

Reply via email to