[infinispan-issues] [JBoss JIRA] (ISPN-1484) The commit command can fail on the originator with a RehashInProgressException and not release the key locks

[Galder Zamarreño (Updated) (JIRA)]

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

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

       Fix Version/s: 5.1.0.BETA3
                      5.1.0.FINAL
                          (was: 5.1.0.CR1)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/600  (was: https://github.com/infinispan/infinispan/pull/600)

    
> The commit command can fail on the originator with a RehashInProgressException and not release the key locks
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-1484
>                 URL: https://issues.jboss.org/browse/ISPN-1484
>             Project: Infinispan
>          Issue Type: Sub-task
>          Components: Locking and Concurrency
>    Affects Versions: 5.0.1.FINAL, 5.1.0.BETA2
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>            Priority: Critical
>             Fix For: 5.1.0.BETA3, 5.1.0.FINAL
>
>
> Because a commit command usually has at least one locked key, it is much more likely than other commands to fail on the originator with a RehashInProgressException. 
> There is no retry mechanism in this case, so the transaction will fail (after we have confirmed the prepare to the TM) and the transaction's keys will not be unlocked (because the failure happens in StateTransferLockInterceptor, which is below the locking interceptor in the invocation chain).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira