[ 
https://issues.apache.org/jira/browse/GEODE-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]
Fred Krone updated GEODE-2661:
------------------------------
    Description: 
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.


  was:
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.



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

Reply via email to