[
https://issues.apache.org/jira/browse/IGNITE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190184#comment-15190184
]
Andrey Kornev commented on IGNITE-2791:
---------------------------------------
Nikolay,
It looks like this condition is treated by CacheContinuousQueryHandler as a
duplicate event (as can be seen from the log message:
{noformat}
DEBUG CacheContinuousQueryHandler - Skip duplicate continuous query message:
CacheContinuousQueryEntry [evtType=CREATED, key=KeyCacheObjectImpl [val=1,
hasValBytes=true], newVal=CacheObjectImpl [val=null, hasValBytes=true],
oldVal=null, cacheId=-1368047377, part=1, updateCntr=1, flags=0,
topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], filteredEvts=null,
keepBinary=false]
{noformat}
which is of course wrong since it's not a duplicate. This issue still occurs
when the continuous query is defined as local and both the filter and the
listener are on the same node.
> Continuous query listener is not notified during concurrent key put.
> --------------------------------------------------------------------
>
> Key: IGNITE-2791
> URL: https://issues.apache.org/jira/browse/IGNITE-2791
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Nikolay Tikhonov
> Priority: Critical
> Fix For: 1.6
>
> Attachments: CacheListenersKillingMe3Main.java
>
>
> Attached the code reproducing the problem. What is evident from the log, is
> that that filter was invoked, but the listener was not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
