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 "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2005/08/17 01:25:54 UTC
[jira] Updated: (DERBY-341) Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained
[ http://issues.apache.org/jira/browse/DERBY-341?page=all ]
Mike Matrigali updated DERBY-341:
---------------------------------
Component: JDBC
> Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-341
> URL: http://issues.apache.org/jira/browse/DERBY-341
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0
> Reporter: Kathey Marsden
> Fix For: 10.2.0.0
>
> If a logical connection has already been obtained, client should disallow XAConnection getConnection if a global transaction has been started and a logical connection has already been obtained
> Repro:
> With the client the script below does not give an error.
> ij> connect 'wombat;create=true';
> ij> disconnect;
> ij> xa_datasource 'wombat';
> ij> xa_connect user 'APP' password 'xxx';
> Connection number: 3.
> ij> -- start new transaction
> xa_start xa_noflags 0;
> ij> xa_getconnection;
> ij> -- Should not be able to get connection again
> xa_getconnection;
> With embedded we get.
> ERROR XJ059: Cannot close a connection while a global transaction is still active.
--
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