I ran the test a bit locally. It seems the ordering is fine either way, however when transactions are enabled sometimes an event is raised twice (I only ever saw a mismatch in size). I tweaked the test to use regular listeners as well and it happens there as well. I would say to log a JIRA and we can look further into it. ]
On Tue, Apr 7, 2015 at 12:46 PM, Pierre Sutra <pierre.su...@unine.ch> wrote: > Hello, > > I have run some tests regarding the ordering properties of the clustered > eventing mechanism in Infinispan > (https://gist.github.com/otrack/0b67dcdae61bb83e0da3). > > When transaction are set to false, clustered listeners receive events in > the same order, as expected. Yet, this is not the case when transactions > are available. I would like to know whether this behavior is expected, > or not, as the documentation does not precise it. > > Cheers, > Pierre > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
