On 4/20/07, A B (JIRA) <[EMAIL PROTECTED]> wrote:
[ https://issues.apache.org/jira/browse/DERBY-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490391 ] A B commented on DERBY-2488: ---------------------------- I haven't heard any comments (good nor bad) about the _v4 patch for this issue. I hope to re-run the regression suites later today to make sure everything is still okay (esp. since some DataSource tests were added to suites.All aftet I posted the patch), and if everything passes then I will likely commit d2488_v4.patch before the end of today (Friday). If people have comments/feedback after that, I can of course address them in subsequent patches. > When loaded by jvm1.6 - EmbeddedConnectionPoolDataSource is not returning a JDBC 4 compliant PooledConnection object > -------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-2488 > URL: https://issues.apache.org/jira/browse/DERBY-2488 > Project: Derby > Issue Type: Bug > Components: JDBC > Affects Versions: 10.2.2.0 > Environment: Run test using JVM 1.6 > Reporter: Stan Bradbury > Assigned To: A B > Attachments: d2488_notTested_v1.patch, d2488_v2.patch, d2488_v3.patch, d2488_v3.stat, d2488_v4.patch, showJDBCdsMetaDataLis.class, showJDBCdsMetaDataLis.class, showJDBCdsMetaDataLis.java, showJDBCdsMetaDataLis.java > > > Updated the problem description to reflect the actual issue [Stan 4/5/07]: EmbeddedConnectionPoolDataSource is not returning a JDBC 4 compliant PooledConnection object > When loaded using JVM 1.6 the JDBC 3.0 data source (org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource) is reporting a JDBC spec compliance level of 4. The DatabaseMetaData.getJDBCMajorVersion method should return the > correct spec compliance level (3) for the JDBC 3.0 data source. The application server that relies on the reported spec compliance level to determine if a statement event listener should be registered will encounter a failure when attemptting to register an event listener with the JDBC 3.0 driver. > Note that the JDBC 4.0 metadata call ..getMetaData().supportsStoredFunctionsUsingCallSyntax() is executed by the JDBC 3.0 driver. This doesn't bother me but seems curious that this is supported by a JDBC 3.0 driver. > Attached is a test case based on the test code from DERBY-8862 (JDBC 4 driver reports incorrect spec complieance level). > Running the test: > set JAVA_HOME to a 1.6 JVM > Compile program > run command: ${JAVA_HOME}/java showJDBCdsMetaDataLis <path-to-database> 3.0 > Using JAVA 6.0 > > "%JAVA_HOME%\bin\java" showJDBCdsMetaDataLis "c:\tstdb102" 3.0 > . . JDBC 3 or less: Using jdbc.EmbeddedConnectionPoolDataSource > Database product: Apache Derby > Database version: 10.2.2.0 - (485682) > Driver name: Apache Derby Embedded JDBC Driver > Driver version: 10.2.2.0 - (485682) > JDBC driver major version: 4 > JDBC driver minor version: 0 > JDBC 4.0 metaData - SFusingCall: true > >> exception thrown: > A non SQL error occured. > java.lang.AbstractMethodError: org.apache.derby.jdbc.EmbedPooledConnection.addStatementEventListener(Ljavax/sql/Statemen > tEventListener;)V > at showJDBCdsMetaDataLis.main(showJDBCdsMetaDataLis.java:103) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
I wonder, is your patch accidentally also solving https://issues.apache.org/jira/browse/DERBY-2559? I won't have time to check this until later...But just pointing out that part of test DataSourceReferenceTest currently is not running with JDBC4 jvms. Myrna Myrna
