Are you doing the urlfetch in an offline call (task queue or cron)? If so, the limit should be higher than 10 seconds as of SDK 1.4.1.
I hope this isn't an "online" call, because it would suck for a user to wait 30 seconds before a page load. You're better off showing the user a loading screen, handing the job to a task queue, then updating the page when the fetch has finished. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Fri, Jun 17, 2011 at 7:42 AM, Luis Montes <monte...@gmail.com> wrote: > I understand why there's a 30 second limit for an http connection to GAE, > but I don't understand why server to server URL fetches get timed out at 10 > seconds. > > Seems like as long as you finish up all your processing in less than 30 you > should be fine. How about upping the URL fetch max to 29 seconds? > > > Thanks, > > Luis > > -- > 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-java@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. > -- 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-java@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.
