[ http://issues.apache.org/jira/browse/DERBY-1254?page=all ]
V.Narayanan resolved DERBY-1254:
--------------------------------
Resolution: Fixed
Derby Info: [Patch Available]
patch has been submitted and committed.
thanx
Narayanan
> XAConnection uses NetConnection as underlying physical connection for
> JDBC4/Java 1.6
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1254
> URL: http://issues.apache.org/jira/browse/DERBY-1254
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0
> Environment: DerbyNetClient
> Reporter: Kristian Waagan
> Assignee: V.Narayanan
> Attachments: DERBY_1254.diff, DERBY_1254.stat
>
> When running under DerbyNetClient (using Derby network server) using Java
> 1.6, XAConnection.getConnection() returns a NetConnection instance instead of
> NetConnection40 instance for the underlying "physical connection". This
> causes AbstractMethod errors for calls in LogicalConnection40 (not yet
> committed). PooledConnection does the correct thing according to the test
> that revealed this problem.
> The XAConnection was obtained by using
> TestUtil.getXADataSource().getXAConnection(). The underlying connection
> object was then obtained with XAConnection.getConnection().
> A new ConnectionTest is on the way as part of DERBY-1180. It will be
> submitted/committed, but not enabled until this bug is fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
