Hello Charles, In fact, I understand this part of your issue, and I believe that there is a good answer from Nick. However, my concern and my answer concerns to the HTTP 500 server error displayed in your screenshots. Sorry for do not let this clear.
On Monday, August 6, 2018 at 8:54:35 PM UTC-4, Charles Batty-Capps wrote: > > I can look into this, but I'm not sure that you carefully read my post. > I'm getting a "process has died unexpectedly" error, NOT a "deadline > exceeded error". > > On Monday, August 6, 2018 at 2:13:27 PM UTC-7, Dan S (Cloud Platform > Support) wrote: >> >> There are many possible reasons to cause this kind of issues such as >> Slow-Loading Apps, >> Performance Settings, Warmup Requests, Delays Associated with Logging >> Delays Associated with UrlFetch… you can find more details about the root >> causes and how to avoid errors in the following documentation[1]. >> >> Also note that while using Java, the runtime may not terminate the >> process, so this could cause problems for future requests to the same >> instance. “To be safe, you should not rely on the DeadlineExceededError, >> and instead ensure that your requests complete well before the time limit.” >> as per docs[2]. >> >> [1] >> https://cloud.google.com/appengine/articles/deadlineexceedederrors#the-request-timer >> [2] >> https://cloud.google.com/appengine/docs/standard/python/how-requests-are-handled#specifying_a_request_deadline >> >> >> On Sunday, August 5, 2018 at 7:56:04 PM UTC-4, Charles Batty-Capps wrote: >>> >>> 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/111e4098-6255-4236-a1cc-0d45ee2728ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
