According to http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/memcache/BaseMemcacheService.html#setErrorHandler(com.google.appengine.api.memcache.ErrorHandler) :
Registers a new ErrorHandler. The handler is called for errors which are not the application's fault, like a *network timeout*. The handler can choose to propagate the error or suppress it. Errors which are caused by an incorrect use of the API will not be directed to the handler but rather will be thrown directly. I'm going to report a bug to the tracker. On Nov 1, 11:04 pm, jon <[email protected]> wrote: > > After taking a look at the documentation it is explicit that put will > > throw an exception in case of an RPC error. > > OK just to make sure that I understand this correctly, > MemcacheServiceException will be thrown when put() encounters an RPC > error (and this is the correct behaviour), therefore the calling code > is expected to handle it. Is that correct? > > > > > > > > > > > See:http://code.google.com/appengine/docs/java/javadoc/com/google/appengi..., > > java.lang.Object, com.google.appengine.api.memcache.Expiration, > > com.google.appengine.api.memcache.MemcacheService.SetPolicy) > > > put > > > void put(java.lang.Object key, > > java.lang.Object value) > > A convenience shortcut, equivalent to put(key, value, null, > > SetPolicy.SET_ALWAYS). > > Parameters: > > key - key of the new entry > > value - value for the new entry > > Throws: > > java.lang.IllegalArgumentException - if the key or value type can't be > > stored as a cache item. They should be Serializable. > > MemcacheServiceException - if server respond with an error. > > > Hope that clear things up. > > > On Fri, Oct 28, 2011 at 12:03 PM, Johan Euphrosine <[email protected]> > > wrote: > > > Could you open a bug on the public issue tracker ? > > >http://code.google.com/p/googleappengine/issues/entry?template=Java%2... > > > > If you can please attach an unittest that exhibit the bad behaviour. > > > > Thanks in advance. > > > > On Fri, Oct 28, 2011 at 12:07 AM, Simon Knott <[email protected]> > > > wrote: > > >> Now that I've got some caffeine in my system, I'll correct myself - it > > >> looks > > >> like the error handler isn't used for "put" operations at all and it's > > >> possible that individual increment calls with fail non-silently as well. > > >> The rest of the calls either use the error handler correctly, or just > > >> fail > > >> silently anyway. > > > >> Cheers, > > >> Simon > > > >> -- > > >> You received this message because you are subscribed to the Google Groups > > >> "Google App Engine" group. > > >> To view this discussion on the web visit > > >>https://groups.google.com/d/msg/google-appengine/-/wqNb9L1OX4cJ. > > >> To post to this group, send email to [email protected]. > > >> To unsubscribe from this group, send email to > > >> [email protected]. > > >> For more options, visit this group at > > >>http://groups.google.com/group/google-appengine?hl=en. > > > > -- > > > Johan Euphrosine (proppy) > > > Developer Programs Engineer > > > Google Developer Relations > > > -- > > Johan Euphrosine (proppy) > > Developer Programs Engineer > > Google Developer Relations -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
