+1 Actually while looking at [1] I encountered the same error you were getting (not the same as the JIRA itself) and thought about how we could remedy that issue on a get as well. Being able to detect this new CacheStoppingException would allow for some options.
[1] https://issues.jboss.org/browse/ISPN-4706 - Will On Thu, Sep 11, 2014 at 10:51 AM, Galder Zamarreño <gal...@redhat.com> wrote: > Hi, > > Re: https://issues.jboss.org/browse/ISPN-4717 > > While investigating [1], I discovered that when clients send operations to > terminated/terminating caches, these are not recovered from. To make this > easier to handle, I’d like to change cache/cachemanager from throwing > IllegalStateException to throwing a new exception that extends > IllegalStateException, e.g. CacheStopping/StoppedException or similar. By > making it IllegalStateException, it should create minimal disruption for > anyone expecting IllegalStateException, although I don’t think this is > documented per se. This, together with a HR error code that accompanies it, > should make it easier for clients to deal with it and retry. > > A new error code will also be added for suspected caches since these are > still propagated to clients. Up until know, this has been dealt with by > checking the error message, but that could break easily, so again, the later > stages of HR 2.0 protocol implementation is good moment for implement these > two things. > > If anyone has any objections, speak up :) > > Cheers, > > [1] https://issues.jboss.org/browse/ISPN-4707 > -- > Galder Zamarreño > gal...@redhat.com > twitter.com/galderz > > > _______________________________________________ > 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
