[
https://issues.apache.org/jira/browse/DERBY-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-341:
---------------------------------
Urgency: Normal
Triaged July 10, 2009: assigned normal urgency.
> Client should disallow XAConnection getConnection() when a global transaction
> has been started and a logical connection has already been obtained
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-341
> URL: https://issues.apache.org/jira/browse/DERBY-341
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.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.
-
You can reply to this email to add a comment to the issue online.
