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-1025) [xa] client XAResource.start() does not commit an active local transaction when auto commit is true
Date Fri, 14 Apr 2006 18:43:02 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1025?page=all ]

Deepa Remesh updated DERBY-1025:

    Attachment: derby-1025-patch2-v1.diff

Thanks Kathey for updating the master files. The diffs in the master file are expected. This
is because the error messages were changed by commit for DERBY-842, svn revision# 393967.
I had my workspace synched up to a older revision when I created the patch.

I am attaching 'derby-1025-patch2-v1.diff' which changes checkDataSource test to test that
starting a global transcation when a local transaction is active will give an exception. The
XA error code is also printed out to verify that we get the expected exception. This patch
will resolve this issue fully.

With this patch, I have run checkDataSource checkDataSource30 tests with embedded and client
frameworks. Please take a look at this patch.

> [xa] client XAResource.start() does not commit an active local transaction when auto
commit is true
> ---------------------------------------------------------------------------------------------------
>          Key: DERBY-1025
>          URL: http://issues.apache.org/jira/browse/DERBY-1025
>      Project: Derby
>         Type: Bug

>   Components: Network Client
>     Reporter: Daniel John Debrunner
>     Assignee: Deepa Remesh
>  Attachments: derby-1025-draft1.diff, derby-1025-draft1.status, derby-1025-patch1-v1.diff,
derby-1025-patch1-v1.status, derby-1025-patch2-v1.diff, derby-1025-patch2-v1.status
> Embedded XAResource.start() implementation commits the active local transaction on the
Connection associated with the XAResource if the connection is auto-commit mode.
> Client incorrectly throws an XAException with the XAER_RMFAIL error code (see DERBY-1024)
> XATest contains a work-around for client (calling commit) with a comment with this bug

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