Is it expected that an exception such as
org.infinispan.remoting.transport.jgroups.SuspectException is
propagated back to the user API?
Does anyone have suggestions on how I should deal with such an error
from the application point of view?
I guess it means the topology changed while performing an operation,
but then I'd expect it to be cared of by Infinispan, and retry on the
new topology if possible.. no?
Tia,
Sanne