I agree with the above. 500 server error occasionally happens over a year I'm working with the AppEngine. I noticed this happens more often with other systems which have HTTP interfaces with my app than with live users. Perhaps reason is that live users mostly read datastore while applications usually perform intensive update operations.
Frustrating is to write in API docs for my site that customers need to retry their request few times if they encounter 500 error. Even more frustrating is that I can do nothing to handle this error within the app. anatoliy On Nov 24, 1:18 pm, Erwin Streur <[email protected]> wrote: > Hi, > > I find the System Status page (http://code.google.com/status/ > appengine) misleading. It almost always shows 100% Availability and > "No significant issues". The non "No significant issues" was on 2nd > November: "Service disruption" even though I have see "Investigating" > in the mean time as well. > > At the application level, our application is regularly returning HTTP > 500 in production (logged as warnings) and we have deployment failures > in development. Given the regular posts in the fora other people are > experiencing the similar problems. So I think that Google should > report something different then "No significant issues", eg. "Minor > issues", "Major issues" > > Any ideas/opinions on this? For example from Google on how they define > "No significant issues"? > > Regards, > > Erwin -- 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.
