You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jonathan Nazario (JIRA)" <ji...@apache.org> on 2012/08/23 17:12:42 UTC
[jira] [Created] (GERONIMO-6383) Geronimo v3.0 (release) - Fail to
unwrap OracleConnection - JDBC4 - TranQL 1.7
Jonathan Nazario created GERONIMO-6383:
------------------------------------------
Summary: Geronimo v3.0 (release) - Fail to unwrap OracleConnection - JDBC4 - TranQL 1.7
Key: GERONIMO-6383
URL: https://issues.apache.org/jira/browse/GERONIMO-6383
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: databases, transaction manager
Affects Versions: 3.0
Environment: System is running Geronimo v3.0 (release) and uses Spring 3.0.5, Oracle11g JDBC driver ojdb6.jar v11.2.0.1.0 which supports JDBC4
Reporter: Jonathan Nazario
Priority: Blocker
*This post covers the problem and temporary solution.*
I put this as a blocker, because I believe is common that people will be using the latest Oracle drivers (thin) which implement JDBC4 and the TranQL 1.7 stack doesn't support it.
*Problem:*
I am using Spring (v3.0.5) JdbcTemplate functionality to execute stored procedures in Oracle 11g database. For some of the calls I need the native connection, but the unwrap failed with the following errors:
{code}
java.lang.ClassCastException: org.tranql.connector.jdbc.ConnectionHandle cannot be cast to oracle.jdbc.OracleConnection
java.lang.AbstractMethodError: org.tranql.connector.jdbc.ConnectionHandle.unwrap(Ljava/lang/Class;)Ljava/lang/Object;
{code}
After working with David from TranQL, it was determined the issue is the Geronimo v.3.0 stack is using TranQL v.1.7 which doesn't support JDBC4 and causes the error during unwrapping the OracleConnection.
*Temporary Solution:*
Geronimo will probably not have this fix until next fix pack. For people who are having the same issue as I, you can use the temporary solution described at the end of this post:
https://jira.codehaus.org/browse/TQL-31?focusedCommentId=306715#comment-306715
This consist of importing a cooked "1.8" RAR into your project which includes new tranql-connector and tranql-connector-oracle-local. And deploying the plan as part of your project to create the JDBC connector.
If you need further help, I open a link in my blog at:
http://jonnazario.blogspot.com/2012/08/geronimo-3-oracleconnection-unwrap.html
*Suggestion for Geronimo*
I don't know if you have CI servers, but at least i didn't notice I wasn't using the OracleConnection until hitting an specific store procedure which requires the native connection. I think is an important test unit to have.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira