db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (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 Tue, 08 May 2007 00:51:15 GMT

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

Daniel John Debrunner commented on DERBY-1025:

In jdbcapi.DataSourceTest there is a piece of code with this comment related to this bug:

        // DERBY-1025.
        // With Embedded, this will give error: 08003 - No current connection
        // But with NetworkServer / DerbyNetClient, the transaction does not
        // appear to be closed, and we actually get a value.

The comment related to the network server does not seem valid any more.
Assuming the test passes since the path through the code that would result in getting a value
back would result in fail() being called.
Should the comment be cleaned up to reflect reality or am I missing something?

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