Re: [infinispan-dev] ClusteredListeners: message delivered twice

2014-02-21 Thread Dan Berindei
On Mon, Feb 17, 2014 at 7:44 PM, William Burns mudokon...@gmail.com wrote: On Mon, Feb 17, 2014 at 7:53 AM, Sanne Grinovero sa...@infinispan.org wrote: On 12 February 2014 10:40, Mircea Markus mmar...@redhat.com wrote: Hey Will, With the current design, during a topology change, an

Re: [infinispan-dev] ClusteredListeners: message delivered twice

2014-02-17 Thread Sanne Grinovero
On 12 February 2014 10:40, Mircea Markus mmar...@redhat.com wrote: Hey Will, With the current design, during a topology change, an event might be delivered twice to a cluster listener. I think we might be able to identify such situations (a node becomes a key owner as a result of the

Re: [infinispan-dev] ClusteredListeners: message delivered twice

2014-02-17 Thread William Burns
On Mon, Feb 17, 2014 at 7:53 AM, Sanne Grinovero sa...@infinispan.org wrote: On 12 February 2014 10:40, Mircea Markus mmar...@redhat.com wrote: Hey Will, With the current design, during a topology change, an event might be delivered twice to a cluster listener. I think we might be able to

[infinispan-dev] ClusteredListeners: message delivered twice

2014-02-12 Thread Mircea Markus
Hey Will, With the current design, during a topology change, an event might be delivered twice to a cluster listener. I think we might be able to identify such situations (a node becomes a key owner as a result of the topology change) and add this information to the event we send, e.g. a flag