You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/04/10 20:18:00 UTC
[jira] Reopened: (DERBY-1009) Embedded ResultSet.getStatement()
does not return the Statement object that created it for a connection
returned from EmbeddedXADataSource
[ http://issues.apache.org/jira/browse/DERBY-1009?page=all ]
Daniel John Debrunner reopened DERBY-1009:
------------------------------------------
> Embedded ResultSet.getStatement() does not return the Statement object that created it for a connection returned from EmbeddedXADataSource
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1009
> URL: http://issues.apache.org/jira/browse/DERBY-1009
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0, 10.1.2.3
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.2.0.0, 10.1.2.4
>
> May also be the case for connections obtained from EmbeddedConnectionPoolDataSource.
> ResultSet.getStatement() is returning the undetlying "physical" java.sql.Statement object, not the brokered object.
> Bug as applications can then get at the underlying "physical" connection and thus continue to
> use a connection that may have been assigned to someone else. Causes FAIL messages in the
> new jdbcapi/XATest, real checks should be added in checkDataSource to ensure all the possible
> connection objects are checked.
--
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