[
http://issues.apache.org/jira/browse/DERBY-1025?page=comments#action_12374403 ]
Daniel John Debrunner commented on DERBY-1025:
----------------------------------------------
There's a chance that changes to the code preceeding that masked the issue, or
maybe the pre-fetching changed behaviour by fetching
rows and causing a commit..
I added this code just before the code you commented out and saw the issue
again:
rs.close();
// ensure a transaction is active to test DERBY-1025
rs = sdh.executeQuery("SELECT * FROM APP.FOO");
> [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 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
