You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@river.apache.org by "Simon IJskes (JIRA)" <ji...@apache.org> on 2012/10/05 10:24:51 UTC

[jira] [Updated] (RIVER-366) Disconnect between javaspace tests and outrigger implementation

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

Simon IJskes updated RIVER-366:
-------------------------------

    Assignee:     (was: Patricia Shanahan)
    
> 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
>            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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira