db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-341) Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained
Date Mon, 06 Jun 2005 18:16:39 GMT
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
    Versions: 10.1.0.0    
    Reporter: Kathey Marsden


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


Mime
View raw message