[ https://issues.apache.org/jira/browse/GEODE-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035504#comment-16035504 ]
ASF subversion and git services commented on GEODE-2661: -------------------------------------------------------- Commit 39bfdccf82ccd86de99f722076d05ad542e468fc in geode's branch refs/heads/release/1.2.0 from [~lgallinat] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=39bfdcc ] GEODE-2661: afterDestroy events fired on non-existent keys during destroy or removeAll. In a client/server topology, afterDestroy events were fired on keys that did not exist for removeAll, remove and destroy. This suppresses those events. cherry-pick 08451526ea5a87e15c4ce609bdf5a0f14fed7d06 from develop > CacheListener gets invoked when an non-existent entry is removed using > removeAll > -------------------------------------------------------------------------------- > > Key: GEODE-2661 > URL: https://issues.apache.org/jira/browse/GEODE-2661 > Project: Geode > Issue Type: Bug > Components: regions > Reporter: Anilkumar Gingade > Assignee: Lynn Gallinat > Labels: storage_2 > Fix For: 1.2.0 > > > PROBLEM: CacheListener.afterDestroy is invoked for an entry which does not > exist. > FIX: Make entry is not a re-destroyed entry. > When a non-existing entry is removed using removeAll from PartitionedRegion > (need to verify this on replicated), the CacheListener's aftrerDestroy > callback method gets invoked. The afterDestroy should not be invoked for > entry which is not present. > How to reproduce. > region.put (k1, v1) > region.put (k2, v2) > // Remove all from client > List keys= Arrays.asList("k1", "k2", "k8"); > region.removeAll(l); > The afterDestroy call back will be invoked for k8. On server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)