db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1236) Verify that applications can't manipulate the transaction state while inside a distributed transaction.
Date Tue, 25 Apr 2006 12:09:07 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1236?page=all ]

Dyre Tjeldvoll updated DERBY-1236:
----------------------------------

    Attachment: derby-1236.v1.diff
                derby-1236.v1.stat

Attiching patch (v1) that adds (negative) testcases for setSavePoint() inside a global transaction.
I have not run derbyall, but I have run XATest.java with java 1.4, 1.5, and 1.6 in embedded
and DerbyNetClient. The test appears to be disabled in 1.3 and fails on trunk in DerbyNet.

Please review

> Verify that applications can't manipulate the transaction state while inside a distributed
transaction.
> -------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1236
>          URL: http://issues.apache.org/jira/browse/DERBY-1236
>      Project: Derby
>         Type: Improvement

>   Components: JDBC
>     Versions: 10.1.2.0
>     Reporter: Rick Hillegas
>     Assignee: Dyre Tjeldvoll
>      Fix For: 10.2.0.0
>  Attachments: derby-1236.v1.diff, derby-1236.v1.stat
>
> The next rev of the JDBC4 spec will clarify that applications may not call the following
methods while inside distributed transactions: setAutoCommit( true ), commit(), rollback(),
and setSavepoint(). We should verify that we conform.

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


Mime
View raw message