I would conclude that whatever result you got is transitory and that you should take it with a grain of salt and possibly retry again! On 11-12-09 11:42 AM, Sanne Grinovero wrote: > 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 > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Hi, On Fri, Dec 9, 2011 at 09:53, Sanne Grinovero<sanne(a)infinispan.org> wrote: > Thanks Vladimir, > I can do that as a short term solution, but do you think we could have > Infinispan care for it in the future? > I don't like to mandate wrapping all invocations to Infinispan in a > try catch block looking for such errors, and maybe others. I am using 5.1.0 BETA 5 and when members are suspected I do not get the exception. Infinispan takes care of it for me. Regards, Slorg1

On 9 December 2011 14:59, Michal Linhard<mlinhard(a)redhat.com> wrote: > I remember having issues related to this: > > https://issues.jboss.org/browse/ISPN-1091 > https://issues.jboss.org/browse/EDG-96 > > isn't HotRod client handling SuspectExceptions at the moment ? Maybe, my problems are with the EmbeddedCacheManager. _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Hi, On Fri, Dec 9, 2011 at 09:53, Sanne Grinovero <sanne(a)infinispan.org&gt; wrote: > Thanks Vladimir, > I can do that as a short term solution, but do you think we could have > Infinispan care for it in the future? > I don't like to mandate wrapping all invocations to Infinispan in a > try catch block looking for such errors, and maybe others. I am using 5.1.0 BETA 5 and when members are suspected I do not get the exception. Infinispan takes care of it for me. Regards, Slorg1 -- Please consider the environment - do you really need to print this email ? _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev