I'm surprised there hasn't been more complaints about memcache from GAE/J users. There's a serious bug in the memcache implementation which breaks its contract. This bug regularly takes my site down, and likely other GAE/J sites too.
According to its Javadoc, ErrorHandler should be invoked when an error is encountered which is not the application's fault, like a network timeout. See: http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/memcache/BaseMemcacheService.html#setErrorHandler(com.google.appengine.api.memcache.ErrorHandler) And yet doPut doesn't make use of ErrorHandler and simply throws MemcacheServiceException. When memcache is playing up an app that uses it heavily (like ours) is virtually inaccessible. I opened this issue over a month ago, it's still not fixed: http://code.google.com/p/googleappengine/issues/detail?id=6236 Please Google make this your highest priority. It has an extremely detrimental effect, yet is easy to fix. And yes, an official response to this post would be nice too. -- 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.
