river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patricia Shanahan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-366) Disconnect between javaspace tests and outrigger implementation
Date Sun, 31 Oct 2010 02:15:19 GMT

    [ https://issues.apache.org/jira/browse/RIVER-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926672#action_12926672
] 

Patricia Shanahan commented on RIVER-366:
-----------------------------------------

Further investigation has revealed that the tests and outrigger are both right, and the root
cause is a bug in com.sun.jini.mahalo.TxnManagerImpl.

The three known examples of this problem all pass if TxnManagerImpl issues an abort on transaction
lease expiration. The TxnManagerImpl code is clearly intended to do so, but uses a test for
whether the transaction is still alive that will always fail for a lease expiration. According
to http://www.jini.org/wiki/Jini_Transaction_Specification "If the granted lease expires or
is cancelled before the transaction manager receives a commit or abort of the transaction,
the manager will abort the transaction."

Transaction participants are notified of aborts, so outrigger can react to abort of those
it has joined without having to poll the transaction manager.

A full QA test will be done before backing out the, apparently incorrect, test change and
checking in the TxnManagerImpl change.

> Disconnect between javaspace tests and outrigger implementation
> ---------------------------------------------------------------
>
>                 Key: RIVER-366
>                 URL: https://issues.apache.org/jira/browse/RIVER-366
>             Project: River
>          Issue Type: Test
>          Components: other
>            Reporter: Patricia Shanahan
>            Assignee: Patricia Shanahan
>            Priority: Minor
>
> Some javaspace tests assume the JavaSpace implementation will reflect the current state
of an involved Transaction, for example, by rejecting actions involving a Transaction whose
manager has discarded it due to lease expiration. The OutRigger implementation caches a Transaction
at the time it joins it, and does not check back with the TransactionManager for each action.

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