[ http://issues.apache.org/jira/browse/DERBY-1025?page=all ]

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

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

Attaching a draft patch 'derby-1025-draft1.diff' which is only for review and 
not for commit. This fixes the repros in the tests XATest.java and 
checkDataSource.java.

I have a question about the expected exceptions in the test 
checkDataSource.java. The exceptions thrown by the client are different from 
what is thrown by the embedded driver. Specifically, I want to make sure this 
is the expected exception in the following case:

---------------------------------------------------------------------------------------------------------------------------------------------------
                conn4.setAutoCommit(false);

                rs4 = s4.executeQuery("select i from autocommitxastart");
                rs4.next(); System.out.println("acxs " + rs4.getInt(1));
                rs4.next(); System.out.println("acxs " + rs4.getInt(1));

                try {
                        xac4.getXAResource().start(xid4a, XAResource.TMNOFLAGS);
                } catch (XAException xae) {
                        showXAException("autocommitxastart expected ", xae);
                }
---------------------------------------------------------------------------------------------------------------------------------------------------
Exception:
autocommitxastart expected  : XAException - XAER_DUPID : Error executing a 
XAResource.start(), Server returned XAER_DUPID
---------------------------------------------------------------------------------------------------------------------------------------------------

With the draft patch, I have only run jdbcapi/checkDataSource.java and 
jdbcapi/XATest.java in client framework. I will be running derbynetclientmats 
shortly. Also, for testing purposes, I have removed the test 
jdbcapi/checkDataSource.java from DerbyNetClient.exclude.

I would appreciate if someone can go through this patch quickly and let me know 
if the changes are okay. 

> [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-draft1.diff, derby-1025-draft1.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

Reply via email to