[infinispan-issues] [JBoss JIRA] (ISPN-2312) TransactionTable does not compute minViewId correctly after NBST was introduced
Adrian Nistor (JIRA)
jira-events at lists.jboss.org
Mon Sep 17 09:57:35 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on ISPN-2312 started by Adrian Nistor.
> 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
> Fix For: 5.2.0.Alpha4
>
>
> 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.
> TransactionTable.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.
--
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
More information about the infinispan-issues
mailing list