river-commits mailing list archives

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

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

Hudson commented on RIVER-366:

Integrated in River-trunk #356 (See [https://hudson.apache.org/hudson/job/River-trunk/356/])
Change tests to eliminate requirement that a transaction stops being available for use in
a JavaSpace write when its lease expires. This affects tests
com/sun/jini/test/impl/outrigger/leasing/UseTxnMgrSpaceLeaseTest.td and com/sun/jini/test/impl/outrigger/leasing/UseTxnMgrSpaceLeaseTestRenew.td

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

View raw message