[infinispan-issues] [JBoss JIRA] (ISPN-2312) TransactionTable does not compute minViewId correctly after NBST was introduced

[Dan Berindei (JIRA)]

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

Dan Berindei updated ISPN-2312:
-------------------------------

        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


Integrated
                
> TransactionTable does not compute minViewId correctly after NBST was introduced
> -------------------------------------------------------------------------------
>
>                 Key: ISPN-2312
>                 URL: https://issues.jboss.org/browse/ISPN-2312
>             Project: Infinispan
>          Issue Type: Bug
>          Components: State transfer, Transactions
>    Affects Versions: 5.2.0.Alpha3
>            Reporter: Adrian Nistor
>            Assignee: Adrian Nistor
>            Priority: Critical
>             Fix For: 5.2.0.Beta1
>
>
> This happens for transactions that arrive via state transfer. The view id of these transactions is currently wrong - it should be the view id in which they were created instead of the current view id at the time they were transferred.
> AbstractTxLockingInterceptor.lockKeyAndCheckOwnership relies on this and consequently does not work correctly for transferred transactions.
> Also TransactionTable listens for JGroup view changes instead of CacheTopology updates. This is another reason minViewId calculation is wrong.
> Another aspect that needs to be considered is the topology id does not change if the update is not caused by a rebalance. In this case the topologyId comparison in AbstractTxLockingInterceptor.lockKeyAndCheckOwnership must not be strict.

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