Re: [infinispan-dev] Suspect Exceptions
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.
If it's mandatory/recommended I would not make it a runtime exception
but something I have to deal with.
Sanne
On 9 December 2011 14:48, Vladimir Blagojevic <vblagoje(a)redhat.com> wrote:
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