db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julius Stroffek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.
Date Tue, 05 Feb 2008 16:36:08 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Julius Stroffek updated DERBY-2871:
-----------------------------------

    Attachment: d2871.stat
                d2871.diff

I added/changed

* missing javadoc with @see tag
* renamed isFinished to performTimeoutRollback
* changed XATransactionTest to use DatabasePropertyTestSetup.setLockTimeouts
* changed System.err.println to Assert.fail with the message

I think that I still have not answered couple of questions:

Kathey:
> On the test in addition to Myrna's comments, do we lose anything by dropping from 1000
connections to 66?

Exactly the same functionality will be tested. Using 1000 connections worked also as something
like a stress test and utilized the database much more.

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

I created DERBY-2953 as that it will log information about rollbacks to derby log in a situation
when I did not know what is/might be causing failures. I also reorganized the code a bit -
one common function is called to rollback/cancel the transaction from different places. I
thought that this change could be committed sooner and it could help to diagnose the problem
after test failures. Now, I have fixies for every possible issue I found and It is also a
bit difficult to divide the patch now to DERBY-2871 and DERBY-2953.

I am running the tests now. derbyall already completed without failures. suites.All are still
running.

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


Mime
View raw message