There are areas where we can definitely manage this exception (which is when we actually do a put), but we had this exception showing up on JSPs of our website, were there is no memcache involved in our code. This outage was taking down much more than it should have.
No word yet from Google about this, other than an informal IRC discussion with one of their dev advocate confirming that SRE addressed the issue around the time we have seen everything coming back to life. Jerome On Oct 26, 8:01 am, Francois Masurel <f.masu...@gmail.com> wrote: > Yep, we got struck by the same outage for about 30 minutes yesterday. > > It's clear that we need to manage such exceptions in our code, we were not > prepared for that. > > But it would be interesting to have some information from Google about what > happened exactly. > > Francois -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
