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] Commented: (DERBY-1025) [xa] client XAResource.start() does not commit an active local transaction when auto commit is true
Date Thu, 13 Apr 2006 19:23:04 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1025?page=comments#action_12374400 ] 

Deepa Remesh commented on DERBY-1025:

I was looking at this and understanding the differences between embedded and client code.
I see the client does not have code to commit in auto-commit mode. I was trying to test my
changes when I found that this problem no longer reproduces with the latest trunk. 

What I tried was - run jdbcapi/XATest.java in client framewrok by commenting out the following
workaround in the test:
            // DERBY-1025 Client only bug
            /*if (TestUtil.isDerbyNetClientFramework()) {
                System.out.println("DERBY-1025 Call conn.commit to avoid exception with client");

I do not get any exceptions. I ran this about 10 times and the test passes without the explicit
"commit" workaround. Can someone please confirm this is right way to repro this issue? If
anyone knows any other repros, please let me know.

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

> 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