When your application fails to handle a request (ie throws out of the request handler rather than returning an error code), appengine treats it as unrecoverable.
This leads it to discard the instance, and to do so it has to terminate any concurrent requests. When an app engine API call happens, it will cause that to fail and record 203. So your causation is probably around the wrong way. I’d look for errors in your logs closely proceeding the 203 on the same instance - your stack trace should tell you what application error is causing this. You probably have a couple of systemic data driven failure (like NPE) on a service that is causing this. Note you can probably still turn off concurrent requesting handling per service, so might be able to isolate more effectively at the cost of greater instances running - not sure about that. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/3d5bfca4-85ef-424a-bbed-cdfcfdd2dbd7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
