[infinispan-issues] [JBoss JIRA] (ISPN-3354) Multiple events on the local node with Infinispan 5.3.0-final

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929413#comment-12929413 ] 

RH Bugzilla Integration commented on ISPN-3354:
-----------------------------------------------

Martin Gencur <mgencur at redhat.com> changed the Status of [bug 1024942|https://bugzilla.redhat.com/show_bug.cgi?id=1024942] from ON_QA to VERIFIED
                
> Multiple events on the local node with Infinispan 5.3.0-final
> -------------------------------------------------------------
>
>                 Key: ISPN-3354
>                 URL: https://issues.jboss.org/browse/ISPN-3354
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Listeners
>    Affects Versions: 5.3.0.Final
>            Reporter: Luca Zenti
>            Assignee: Pedro Ruivo
>            Priority: Critical
>              Labels: 620
>             Fix For: 6.1.0.Final
>
>         Attachments: TestInfinispanDuplicatedEvents.java
>
>
> After upgrading to Infinispan 5.3.0-final I found a strange "intermittent" problem in my application. Digging a bit deeper, I found out it is due to CacheEntry events raised twice for some keys on the local node (the node where the cache operation is invoked).
> I was able to reproduce the problem and I wrote the attached test case.
> The problem happens regardless of the cluster mode, but only with non-transactional caches. I think this is due to the fact that with transactional caches the events are raised on commit.
> Also, my application used to work with an interceptor rather than an event listener, so I actually found the problem when I saw my interceptor being occasionally executed 3 times with 2 nodes.
> I'm not sure whether the command and the chain of interceptor is really meant to be executed twice on the local node, but the consequent behaviour on the events sounds like a bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira