Thankfully I saw the error while testing a newly deployed version, and before taking it live. That would have been very embarrassing -- the day before had already encuntered a 30 minute window of up to 20% of memcache errors, which affected our clients as well (in the form of 500 error pages, which IMO should not happen due to Memcache in the first place, but that's another story).
http://code.google.com/status/appengine/detail/memcache/2012/12/05#ae-trust-detail-memcache-get-error_rate I can't help it, but I have to (yet again) complain about reliability of App Engine. It's a marvellous piece of technology, and feature-wise it has come such a long way since I started using it two years ago. But it's causing me more and more headache the more mature it gets. I was expecting it to be the other way round when I started. I'm doing a presentation about GAE at the Berlin Java User Group next week. While I will praise all the cool features of App Engine, I have the feeling that I won't convert a single attendee once I mention the errors we keep running into. Which is sad, because I do want GAE to prosper. Cheers, Per On Thursday, December 6, 2012 6:08:51 AM UTC+1, Takashi Matsuo (Google) wrote: > > Hi prashant, > > It's good to see the comment on the issue saying that your app is now OK. > Thanks for reporting! > > > On Wed, Dec 5, 2012 at 7:32 PM, prashant <prashan...@gmail.com<javascript:> > > wrote: > >> Users are impacted. Production issue has been raised. >> >> http://code.google.com/p/googleappengine/issues/detail?id=8511 >> >> Can you please check. >> >> We are getting this exception & a 500 error. >> >> java.lang.NoClassDefFoundError: Could not initialize class >> com.google.appengine.api.datastore.DatastoreAttributes >> at >> com.google.appengine.api.datastore.AsyncDatastoreServiceImpl.getDatastoreAttributes(AsyncDatastoreServiceImpl.java:985) >> at >> com.google.appengine.api.datastore.AsyncDatastoreServiceImpl.getDatastoreType(AsyncDatastoreServiceImpl.java:977) >> at >> com.google.appengine.api.datastore.AsyncDatastoreServiceImpl.get(AsyncDatastoreServiceImpl.java:284) >> at >> com.google.appengine.api.datastore.DatastoreServiceImpl$1.runInternal(DatastoreServiceImpl.java:78) >> at >> com.google.appengine.api.datastore.DatastoreServiceImpl$1.runInternal(DatastoreServiceImpl.java:75) >> at >> com.google.appengine.api.datastore.TransactionRunner.runInTransaction(TransactionRunner.java:31) >> at >> com.google.appengine.api.datastore.DatastoreServiceImpl.get(DatastoreServiceImpl.java:75) >> at >> com.google.appengine.api.datastore.DatastoreServiceImpl.get(DatastoreServiceImpl.java:62) >> at >> com.google.apphosting.runtime.jetty.DatastoreSessionStore.getSession(DatastoreSessionStore.java:82) >> at >> com.google.apphosting.runtime.jetty.SessionManager.loadSession(SessionManager.java:338) >> >> >> >> >> >> Thanks. >> >> -- >> 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/-/P9EyMaLNEt4J. >> To post to this group, send email to >> google-a...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> google-appengi...@googlegroups.com <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> > > > > -- > Takashi Matsuo | Developers Advocate | tma...@google.com <javascript:> > > -- 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/-/yIu2J1rgY1YJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
