[
https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570673#action_12570673
]
Knut Anders Hatlen commented on DERBY-2871:
-------------------------------------------
It seems like Dan's comment from 05/Feb/08 12:19 PM hasn't been addressed.
ResourceAdapterImpl.cancelXATransaction() calls findConnection() twice. Is that
intentional?
Is the comment about synchronization in ResourceAdapter.cancelXATransaction()
still valid in the latest patch?
Could you comment on why you call DatabasePropertyTestSetup.setLockTimeouts()
in XATransactionTest.suite()? As far as I can see, the timeout values specified
(20 sec deadlock, 60 sec wait) are the same as the default values, so it
doesn't change anything.
Tiny nit: assertTrue(xaConn[i] != null) could be replaced with
assertNotNull(xaConn[i]).
> 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.diff, d2871.diff, d2871.stat, d2871.stat, 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.
