[infinispan-issues] [JBoss JIRA] (ISPN-1346) Transactional listeners method order problem

[RH Bugzilla Integration (JIRA)]

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

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

Tomas Sykora <tsykora at redhat.com> changed the Status of [bug 841887|https://bugzilla.redhat.com/show_bug.cgi?id=841887] from ON_QA to VERIFIED
                
> Transactional listeners method order problem
> --------------------------------------------
>
>                 Key: ISPN-1346
>                 URL: https://issues.jboss.org/browse/ISPN-1346
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Listeners
>    Affects Versions: 5.0.0.FINAL
>         Environment: fedora, windows
>            Reporter: Tomas Fecko
>            Assignee: Mircea Markus
>              Labels: jdg6, listeners, transaction
>             Fix For: 5.1.6.FINAL, 5.2.0.ALPHA2, 5.2.0.FINAL
>
>
> I'm using listeners as from the @Listener javadoc examples. When I register listener on VM where the cache is and put items to it, the methods of my listener are called in this order:
> @TransactionRegistered
> startTransaction
> @CacheEntryCreated
> handleEvent
> @CacheEntryCreated
> handleEvent
> @TransactionCompleted
> endTransaction
>  
> which is as it should be, but when I register listener on second node, and put to cache in first node, methods on listener on second node are called in order:
> handleEvent
> handleEvent
> startTransaction
> endTransaction

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira