[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2017-03-31 Thread 'Nick (Cloud Platform Support)' via Google App Engine
Hey Chris, >From reading the thread history, it seems that there are potentially two issues brought up by kyeongwook Ma and Dustin Oprea. Although both see an expired context, one is about UrlFetch calls and the other is about Datastore API calls. The mechanism underlying potentially both of th

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2017-03-31 Thread Chris Olsen
I get this error quite often as well. I am using standard environment, and as was mentioned, the request itself is not a long one, but under a second. On Tuesday, August 9, 2016 at 8:29:30 AM UTC-6, kyeongwook Ma wrote: > > Hi GAE support, > > I am a developer using the GAE with Golang and gin. >

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2016-09-06 Thread 'Nicholas (Google Cloud Support)' via Google App Engine
Also, just to be certain, are you using the standard or flexible environment? On Tuesday, August 9, 2016 at 10:29:30 AM UTC-4, kyeongwook Ma wrote: > > Hi GAE support, > > I am a developer using the GAE with Golang and gin. > > I included urlfetch in the service to use a third party service (for

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2016-09-06 Thread 'Nicholas (Google Cloud Support)' via Google App Engine
Dustin, It's not entirely clear what is happening but it seems like a go *context.Context * is expiring before the request terminates, causing a *panic* to bubble up which is not being handled. Could you provide a trimmed down version of your handle

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2016-08-31 Thread Dustin Oprea
I have this error constantly, though I'm not explicitly using urlfetch. I'm just using datastore and memcache. As I'm in the early stages of this project, I only recently noticed it happening more frequently after I implemented session management on top of datastore and memcache, but, now, as I

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2016-08-16 Thread 'Nicholas (Google Cloud Support)' via Google App Engine
Hi there, Have you had a chance to review some of the recommendations posted here by Evan and myself? Was any of the advice helpful in troubleshooting? If this still affects you, could you provide some of the information requested in my previous post? Looking forward to hearing from you! On

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2016-08-11 Thread 'Nicholas (Google Cloud Support)' via Google App Engine
Apologies for the follow-up, here's an example of a trace detail showing exact latencies for various RPC calls. This can be very useful. On Tuesday, August 9, 2016 at 10:29:30 AM UTC-4, kyeongwook Ma wrote: > > Hi GAE support,

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2016-08-11 Thread 'Nicholas (Google Cloud Support)' via Google App Engine
Thanks for sharing your issue here. Based on the expired context error you are receiving, I suspect Evan is most likely correct here. Nevertheless, more information would definitely help with narrowing down the range of possible issues here: - You mention sending 30 to 40 consecutive urlfet

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

2016-08-10 Thread Evan Jones
Are you using the Standard Environment? I think this happens if you are trying to do work for longer than the App Engine request timeout (60 seconds), or after you have responded to the original web request. The key words in this error are "context expired", which means this is some sort of tim