[google-appengine] Re: "The process handling this request has unexpectedly died... (Error Code 203)"

2018-08-05 Thread Charles Batty-Capps
Your post may have given me an idea, but the root cause isn't what you think. 
We always use a REST framework for all our services (the latest version of 
Jersey currently), so I am 100% certain an unexpected application level 
exception results in a 500 error and the stacktrace is logged by an Exception 
handler in Jersey. We never see anything in the logs except for the process 
death error when this happens. 

It stands to reason that maybe an exception is being thrown in the Jersey layer 
before it reaches the HTTP layer, and somehow nothing is logged in this case.

I'll investigate options with Jersey. Maybe there's a thread pool that needs 
reconfiguring or something.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/2d928357-c828-43ab-a365-1d28e3566fde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] python 3.7 standard runtime release schedule?

2018-08-05 Thread Eric G
Apologies if this has already been asked, but now that python 3.7 standard 
has been announced, what is the timeframe?  Is there an alpha signup yet?

Thanks.
Eric

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/99d7d2f5-cea4-47c9-af39-c411fc1e4992%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[google-appengine] Re: "The process handling this request has unexpectedly died... (Error Code 203)"

2018-08-05 Thread Nick
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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.