[infinispan-issues] [JBoss JIRA] (ISPN-1346) Transactional listeners method order problem
Mircea Markus (JIRA)
jira-events at lists.jboss.org
Wed Jun 27 09:20:13 EDT 2012
[ https://issues.jboss.org/browse/ISPN-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703541#comment-12703541 ]
Mircea Markus commented on ISPN-1346:
-------------------------------------
This is no longer an issue. The sequence is now (5.2) the same on both originator and the remote node: started, created and completed. Added unit test to confirm and document this behavior (TxListenerInvocationSequenceTest).
> 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: listeners, transaction
> Fix For: 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
More information about the infinispan-issues
mailing list