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 "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2006/06/02 18:27:34 UTC
[jira] Resolved: (DERBY-1148) Client XA getTransactionIsolation()
does not return the correct isolation level when rejoining a global
transaction
[ http://issues.apache.org/jira/browse/DERBY-1148?page=all ]
Kathey Marsden resolved DERBY-1148:
-----------------------------------
Fix Version: 10.1.2.5
Resolution: Fixed
Derby Info: (was: [Patch Available])
Submitted to 10.1
Date: Fri Jun 2 09:15:08 2006
New Revision: 411202
URL: http://svn.apache.org/viewvc?rev=411202&view=rev
Thanks Deepa!
> Client XA getTransactionIsolation() does not return the correct isolation level when rejoining a global transaction
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1148
> URL: http://issues.apache.org/jira/browse/DERBY-1148
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.2.0.0
> Reporter: Kathey Marsden
> Assignee: Deepa Remesh
> Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.5
> Attachments: SetIsolationUsingSQL.java, XACheckIsolation.java, XACheckIsolation_2.java, XA_TransactionIsolation.html, derby-1148-draft1.diff, derby-1148-draft1.status, derby-1148-javadoc.diff, derby-1148_10.1.diff, derby-1148_10.1.status, derby-1148_v1.diff, derby-1148_v1.status, derby-1148_v2.diff, derby-1148_v2.status
>
> When rejoining a global transaction, client does not report the correct isolation level with a
> getTransactionIsolation(). The server side isolation should be ok I think.
> This was discovered when testing the fix for DERBY-1044. After the fix for DERBY-1044, there is a new diff in the test, but the fix for DERBY-1044 just exposed this issue. The output for the test was correct before by circumstance.
> I will put comments with this bug in checkDataSource test.
> // now re-join the transaction, should pick up the read-only
> // and isolation level from the transaction,
> // holdability remains that of this handle.
> xar.start(xid, XAResource.TMJOIN);
> printState("re-join X1", cs1);
> xar.end(xid, XAResource.TMSUCCESS);
--
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