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] Commented: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.
Date Wed, 09 Jan 2008 17:40:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557350#action_12557350

Julius Stroffek commented on DERBY-2871:

Changes in xa transaction timeout:
* added a code to print a text message to a log file when the global transaction will get
rolled back.
* joined a code performing a rollback of the global transaction on both embedded and network
drivers. The transaction is now atomically (XATransactionState lock is obtained only once)
disassociated from the resource and rolled back. The common code is placed in XATransactionState
* a reference to the ResourceAdapter instance was necessary to be present in DRDAXAProtocol/XADatabase
and it is captured from EmbedXADataSource during a creation of a connection in XADatabase

Changes in XATransactionTest:
* The number of connections created was reduced from 1000 to 66.
* All the references to connections are kept in an array so that no optimization will garbage
collect them before the transaction will get rolled back by the proper code tested. All the
connections are closed manually at the end of the test.
* The long running statement was rewritten to use system tables thus the test will no longer
need an appropriate number of records in a test table (thus less connections might be created).
* derby.locks.waitTimeout and derby.locks.deadlockTimeout are being stored in test setup and
changed to high enough values and changed back at tearDown. jdbcapi/SetTransactionIsolationTest
changes both of these to 3 without restoring them back and this was causing issues with a
* a list of global transactions in progress is dumped when the test fails in case there are
pending transactions that were supposed to be rolled back

Dyre (response to the comment at DERBY-2953):
I am also not quite clear about the policy when to write a javadoc comment and when not. I
think I have written javadoc comments for all new methods/classes except when the comment
is present in the superclass or method of the superclass and there is nothing new to be written
in the implementation. I can copy the comment from the superclass but I do not see a benefit
of doing this.

Thanks for reviewing the patch.

> XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned
> ------------------------------------------------------------------------------------------------------
>                 Key: DERBY-2871
>                 URL: https://issues.apache.org/jira/browse/DERBY-2871
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>         Environment: OS: HP-UX v1.11 i 
> JDK: HP 
>            Reporter: Henri van de Scheur
>            Assignee: Julius Stroffek
>            Priority: Minor
>         Attachments: d2871-test.diff, d2871-test.stat, d2871.diff, d2871.diff, d2871.stat,
> 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/

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message