Why getting WebLogic Connection when using Oracle Driver?

Question

Does anyone know why I would be getting back an instance of weblogic.jdbc.rmi.SerialConnection
when retrieving a connection out of the connection pool, via my JDBC TX DataSource,
when my JDBC Connection pool is configured to use oracle.jdbc.OracleDriver. Seems
that since I'm using the Oracle driver I should not be getting back this WebLogic
connection.
Any insight is appreciated :)
thanks,
Dan

Answer 1

innumonenu wrote:
Even we are facing the same problem of ClassCastException when we try to cast to
OracleCallableStatement from the weblogic pool made of Oracle JDBC driver.
What is the URL which explains,
"Our wrappers do provide access to various non-standard
Oracle methods, and we document how to cast (to our concret class or to an interface
we define) in order to access these calls." as said by Joseph.http://e-docs.bea.com/wls/docs70/jdbc/thirdparty.html#1043705
>
>
"Dan Branley" <[email protected]> wrote:
Joseph,
Thanks for the insight. This answers a lot of questions. I appreciate
the thorough
explanation. Your assumption is correct. I am trying to use an Oracle
extension,
specifically I need to call PreparedStatement.setBlob() passing an instance
of
an Oracle BLOB.empty_lob(). I'll take a look at the WLS documentation
for an
alternative.
thanks,
Dan Branley
Joseph Weinstein <[email protected]> wrote:
We never give application code direct access to pooled connections.We
always
supply a wrapper class. These wrapper classes have various extra functionality,
such as cooperating under-the-covers with the transaction coordinator
to provide
EJB/UserTransaction transactional semantics/guarantees, regardless of
the number
of EJBs involved in a given transaction. For instance, when in an EJB/UserTransaction,
our wrapper will cheerfully ignore if application code calls a Connection.commit().
The
application code has no idea really when the transaction is done and
commitable, only
the transaction coordinator does. Most simply, our pools guarantee that
whatever
application reserves a pool connection will have sole use of it until
they close the connection
to return it to the pool. If we allowed direct access to a pooled connection,
one application
could cache the reference, and re-use it later when we presumed to allow
another user to
use it from the pool. Some of our wrapper objects are RMI-enabled so
they work in
external client JVMs and will do JDBC over the wire to the weblogicserver
and it's
pool connections. This wayt application code need not change to work
inside or
outside weblogic.
I suspect this question is because you want to use some of Oracle's
non-standard
extensions to JDBC. Our wrappers do provide access to various non-standard
Oracle methods, and we document how to cast (to our concret class or
to an interface we
define) in order to access these calls. Not all calls can be successfully
proxied by our wrappers
because some Oracle methods (which claim to take java.sql object asarguments)
actually
require oracle specific classes, and reject our proxies, even if they
are standard JDBC objects.
Joe
Dan Branley wrote:
Does anyone know why I would be getting back an instance of weblogic.jdbc.rmi.SerialConnection
when retrieving a connection out of the connection pool, via my JDBCTX DataSource,
when my JDBC Connection pool is configured to use oracle.jdbc.OracleDriver.Seems
that since I'm using the Oracle driver I should not be getting backthis WebLogic
connection.
Any insight is appreciated :)
thanks,
Dan