db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DERBY-1025) [xa] client XAResource.start() does not commit an active local transaction when auto commit is true
Date Thu, 29 Mar 2007 20:07:25 GMT

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

Myrna van Lunteren reopened DERBY-1025:

I believe this was incorrectly closed.
Although I don't see the XAID_DUP error, so there was improvement, it seems to me the transaction
is still active.

checkDataSource has I think a mistake in it that gave the impression this was fixed:

    try {
         rs4.next(); System.out.println("acxs " + rs.getInt(1))
    } catch (SQLException sqle) {
         System.out.println("autocommitxastart expected " + sqle.getMessage());

We're doing rs4.next(), but then attempt to get a value out of rs, rather than rs4. rs has
been closed way before this point, so not surprisingly, this gives an sqlexception.

When I change rs.getInt(1) to rs4.getInt(1), things work unchanged for embedded. However,
with DerbyNetClient, we get different behavior; we happily get a value returned (3). 

> [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: Deepa Remesh
>             Fix For:,
>         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,
> 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.
You can reply to this email to add a comment to the issue online.

View raw message