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 23:35:01 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1025?page=all ]

Deepa Remesh updated DERBY-1025:
--------------------------------

    Attachment: derby-1025-10.1.diff
                derby-1025-10.1.status

Attaching 'derby-1025-10.1.diff' for 10.1 branch. A direct merge does not work because the
test checkDataSource is not enabled for client in 10.1. 

I ran derbynetclientmats using Sun JDK 1.4.2 on Windows XP. I also ran the test jdbcapi/XATest
on client and embedded frameworks. Please look at this patch.

NOTE: 
There are two pending patches attached to this issue:
* derby-1025-10.1.diff for 10.1 branch
* derby-1025-patch2-v1.diff for trunk (changes to the test checkDataSource.java)


> [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-10.1.diff, derby-1025-10.1.status, 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
number.

-- 
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