db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1148) Client XA getTransactionIsolation() does not return the correct isolation level when rejoining a global transaction
Date Thu, 01 Jun 2006 21:06:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1148?page=all ]

Deepa Remesh updated DERBY-1148:

    Attachment: derby-1148_10.1.diff

Attaching a patch "derby-1148_10.1.diff" for 10.1 branch. There were conflicts with a direct
merge, hence attaching a patch. With the patch, I ran derbynetclientmats using Sun jdk1.4.2
on Windows XP.  No failures.

Please note that there are two pending patches attached to this issue:
1. derby-1148-javadoc.diff - for trunk
2. derby-1148_10.1.diff - for 10.1 branch

Please take a look at these. 

> 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:
>     Reporter: Kathey Marsden
>     Assignee: Deepa Remesh
>      Fix For:,
>  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,
> 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:
For more information on JIRA, see:

View raw message