db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4558) Issue (regression) with IBM JDK and Derby 10.5.3.0 and an OpenJPA testcase
Date Fri, 19 Feb 2010 21:26:27 GMT
Issue (regression) with IBM JDK and Derby 10.5.3.0 and an OpenJPA testcase
--------------------------------------------------------------------------

                 Key: DERBY-4558
                 URL: https://issues.apache.org/jira/browse/DERBY-4558
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.5.3.0
            Reporter: Kevin Sutter


The OpenJPA project just moved from Derby 10.2.2.0 to Derby 10.5.3.0.  We have found that
one of our testcases no longer works after this upgrade.  But, the failure only happens with
the IBM JDK.  The Sun JDK (and Apple JDK) seem to work just fine.

The testcase is related to executing stored procedures.  You can find the testcase in the
Apache OpenJPA project:

TestNativeQueryProcedures.testNoReturnMultiParamProcedure (org.apache.openjpa.persistence.jdbc.query)

junit.framework.AssertionFailedError: Caught unexpected exception executing stored procedure:
Method resolution for signature org.apache.openjpa.persistence.jdbc.query.procedure.DerbyProcedureList.addSuffixToName(java.lang.String,
java.lang.String) was ambiguous. (No single maximally specific method.) {{ call ADD_SUFFIX_TO_NAME
(?, ?) }} [code=20000, state=42X73]
at junit.framework.Assert.fail(Assert.java:47)
at org.apache.openjpa.persistence.jdbc.query.TestNativeQueryProcedures.testNoReturnMultiParamProcedure(TestNativeQueryProcedures.java:227)
Show details » 
« Hide details
junit.framework.AssertionFailedError: Caught unexpected exception executing stored procedure:
Method resolution for signature org.apache.openjpa.persistence.jdbc.query.procedure.DerbyProcedureList.addSuffixToName(java.lang.String,
java.lang.String) was ambiguous. (No single maximally specific method.) {{ call ADD_SUFFIX_TO_NAME
(?, ?) }} [code=20000, state=42X73]
at junit.framework.Assert.fail(Assert.java:47)
at org.apache.openjpa.persistence.jdbc.query.TestNativeQueryProcedures.testNoReturnMultiParamProcedure(TestNativeQueryProcedures.java:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at junit.framework.TestCase.runTest(TestCase.java:154)
at org.apache.openjpa.persistence.test.AbstractPersistenceTestCase.runTest(AbstractPersistenceTestCase.java:514)
at junit.framework.TestCase.runBare(TestCase.java:127)

We have only experienced this with the IBM JDK, both at the Java 6 SR5 and SR7 fix levels.

Thanks,
Kevin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message