db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1025) [xa] client XAResource.start() does not commit an active local transaction when auto commit is true
Date Mon, 07 May 2007 19:53:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494117
] 

Kathey Marsden commented on DERBY-1025:
---------------------------------------

Looking at the test, I think to test whether the cursor is closed we needed to create the
statement with CLOSE_CURSRS_AT_COMMIT.  Making that change, client seems to work as expected.
 We get SQLState XCL16, but embedded is getting 08003 - No current connection, which I think
is wrong. The connection should still be valid. It is only the resultset that is closed. I
will open another issue for that and submit the test change.


> [xa] client XAResource.start() does not commit an active local transaction when auto
commit is true
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1025
>                 URL: https://issues.apache.org/jira/browse/DERBY-1025
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>            Reporter: Daniel John Debrunner
>         Assigned To: Kathey Marsden
>             Fix For: 10.1.3.1, 10.2.1.6
>
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message