[infinispan-issues] [JBoss JIRA] (ISPN-3192) Concurrent TreeCache.move() calls with the same destination lose data

[Galder Zamarreño (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño updated ISPN-3192:
-----------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 5.3.0.Final
                       (was: 6.0.0.Final)
       Resolution: Done

    
> Concurrent TreeCache.move() calls with the same destination lose data
> ---------------------------------------------------------------------
>
>                 Key: ISPN-3192
>                 URL: https://issues.jboss.org/browse/ISPN-3192
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Tree API
>    Affects Versions: 5.3.0.CR1
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 5.3.0.Final
>
>
> The move method reads the contents of the destination node in the transaction/invocation context before locking it. 
> If there are multiple parallel movers with the same destination, some of the moved nodes might be lost. This sometimes happens in NodeMoveAPIPessimisticTest, causing random failures.
> Note that even if the move() method locks the destination node, it will still be possible for the user to read the destination node in the same transaction and cause data loss. The move() method documentation should warn about this.

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