[
https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564967#action_12564967
]
Kathey Marsden commented on DERBY-2871:
---------------------------------------
Thank you for looking at this issue. I got a bit confused about which changes
were part of this issue and which were part of DERBY-2953. Are the code
changes necessary for the test to pass with its changes or were the two issues'
patches just combined for convenience?
On the code changes I got a bit confused with the XATransationState.isFinished
instance variable changes. isFinished is documented as:
/** Has this transaction been finished (committed
* or rolled back)? */
But the makes isFinshed = true with the XATransactionState constructor, which I
didn't quite understand. The transaction hasn't been committed or rolled back
at that point. It looks like isFinished is only set to false in
setTransactionTimeout which doesn't seem quite right.
On the test in addition to Myrna's comments, do we lose anything by dropping
from 1000 connections to 66?
The javadoc still says 1000 connections.
> XATransactionTest gets XaException: Error executing a XAResource.commit(),
> server returned XAER_PROTO.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2871
> URL: https://issues.apache.org/jira/browse/DERBY-2871
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.1.4
> Environment: OS: HP-UX v1.11 i
> JDK: HP 1.5.0.03
> Reporter: Henri van de Scheur
> Assignee: Julius Stroffek
> Priority: Minor
> Attachments: d2871-test.diff, d2871-test.stat, d2871.diff,
> d2871.diff, d2871.stat, d2871.stat, DERBY-2871_020108.diff
>
>
> Method: org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest
> Signature:
> %XAER_PROTO : Error executing a XAResource.commit(), server returned
> XAER_PROTO%
> Also see:
> http://dbtg.thresher.com/derby/test/10.3.1.0_RC/jvm1.5/testing/testlog/hpux/548006-suitesAll_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
