[
https://issues.apache.org/jira/browse/GEODE-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090011#comment-16090011
]
ASF subversion and git services commented on GEODE-3204:
--------------------------------------------------------
Commit 0bce1eaffd1b8c0f482519ec47ea43231e8f40f1 in geode's branch
refs/heads/develop from [~eshu]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0bce1ea ]
GEODE-3204: txApplyInvalidate in AbstractRegionMap on farside does not update
on a region entry with removed token.
> txApplyInvalidate in AbstractRegionMap on farside should not update the entry
> if it is a removed token
> ------------------------------------------------------------------------------------------------------
>
> Key: GEODE-3204
> URL: https://issues.apache.org/jira/browse/GEODE-3204
> Project: Geode
> Issue Type: Bug
> Components: transactions
> Affects Versions: 1.3.0
> Reporter: Eric Shu
> Assignee: Eric Shu
>
> When tx invalidates on a region entry with Token.REMOVED_PHASE2 (without
> forceNewEntry), it could update a region entry going to be removed from the
> AbstractRegionMap. In some race cases, a new tx create could be lost, as a
> txApplyPut could update on the entry with INVALIDATE token without executing
> the putEntryIfAbsent (does not recognize the entry is being removed from the
> AbstractRegionMap, as the entry is not Token.REMOVED_PHASE2).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
