The CacheListener is a local observer: it sees changes to the local copy of the cache. If a transaction is started on the "master" node (master for a given interaction, otherwise nodes need not be symmetric), and it is rolled back, changes are not replicated to the slave nodes. Thus on slave nodes, the CacheListener is not notified of any change on rollback. So the only problem is that the master node's CacheListener IS notified even in case of rollback.
So you don't need the workaround if, on the master node, you don't need the notification. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268955#4268955 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268955 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
