Python supports asynchronous URLFetch, but Java doesn't. So if we need to do any asynchronous URLFetching, our only option is to use the TaskQueue, right?
Well, I always thought our apps had 30 seconds to complete their business. Since URLFetch calls can take up to 10 seconds to complete, 30 seconds is more than enough. So I wrote an "asynchronous_urlfetch" function which simply used the TaskQueue to post a URL to a webhook which called URLFetch. Not as good as the Python way, but it should work just fine. But it doesn't! My logs are full of "500 ... Request was aborted after waiting too long to attempt to service your request." for the aforementioned webhook. Aparently, rather than giving the normal 30 seconds, App Engine is killing my TaskQueues after only 10! So if my URLFetch takes 10 seconds, the entire webhook dies! Am I interpreting this right? Are TaskQueues really getting killed after 10 rather than 30 seconds? If so, could we please get this rectified? And, really, time spent waiting on URLFetch should not count against us, anyway! That's outside of our control and is certainly NOT indicative of problems with our apps.
-- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
