You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2016/05/18 12:26:12 UTC

[jira] [Commented] (IGNITE-2620) Extra 'entry expired' events

    [ https://issues.apache.org/jira/browse/IGNITE-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288872#comment-15288872 ] 

Semen Boikov commented on IGNITE-2620:
--------------------------------------

Original issue with extra events is already fixed, but problem with broken synchronization in GridCacheMapEntry.onTtlExpired still exists.

> Extra 'entry expired' events
> ----------------------------
>
>                 Key: IGNITE-2620
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2620
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.5.0.final
>            Reporter: Semen Boikov
>            Assignee: Semen Boikov
>
> Added test reproducing issue: IgniteCacheEntryListenerExpiredEventsTest (more then 1 event can be fired for single entry expiration).
> Very suspicious place is GridCacheMapEntry.onTtlExpired: even when entry is obsolete it calls 'clearIndex' and 'releaseSwap' (these calls should be prohibited for obsolete entry).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)