[
https://issues.apache.org/jira/browse/GEODE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134469#comment-15134469
]
ASF subversion and git services commented on GEODE-915:
-------------------------------------------------------
Commit f3dd3353deb154ade18136781cc18308d3f615dd in incubator-geode's branch
refs/heads/develop from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f3dd335 ]
GEODE-915: add FORCE_INVALIDATE_EVENT
If the system property gemfire.FORCE_INVALIDATE_EVENT
is set to true then afterInvalidate on CacheListeners will be called even
if the entry does not exist or if the entry is already invalid.
> invalidate event when entry does not exist or already invalid
> -------------------------------------------------------------
>
> Key: GEODE-915
> URL: https://issues.apache.org/jira/browse/GEODE-915
> Project: Geode
> Issue Type: New Feature
> Components: core
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
>
> When a Region invalidate finds that the entry does not exist or is already
> invalid it does not invoke afterInvalidate on the CacheListener. Some users
> have requested that afterInvalidate be invoked even in these cases.
> What was done to for them was a system property named
> "gemfire.FORCE_INVALIDATE_EVENT" was added. If it was set to "true" then
> afterInvalidate was invoked even if the entry did not exist or was already
> invalid. In both these cases the oldValue on the EntryEvent passed to
> afterInvalidate was set to null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
