Hey Patrice, The URLFetch code that I posted is not in production because it does not work for me. The request always times out after 10 seconds no matter what number I set in the timeout. And the funny thing is the URLFetch code works when I deploy it locally and test. But when I upload it to GAE, it starts timing out.
I tried setting the timeout in the xml but got an XML parse error. This is what I tried. Am I doing this wrong? <?xml version="1.0" encoding="utf-8"?> <appengine-web-app xmlns="http://appengine.google.com/ns/1.0";> <application>saseatavailability</application> <version>1</version> <!-- Allows App Engine to send multiple requests to one instance in parallel: --> <threadsafe>true</threadsafe> <appengine.api.urlfetch.defaultDeadline>10.0</appengine.api.urlfetch.defaultDeadline> <!-- Configure java.util.logging --> <system-properties> <property name="java.util.logging.config.file" value="WEB-INF/logging.properties"/> </system-properties> <!-- HTTP Sessions are disabled by default. To enable HTTP sessions specify: <sessions-enabled>true</sessions-enabled> It's possible to reduce request latency by configuring your application to asynchronously write HTTP session data to the datastore: <async-session-persistence enabled="true" /> With this feature enabled, there is a very small chance your app will see stale session data. For details, see http://code.google.com/appengine/docs/java/config/appconfig.html#Enabling_Sessions --> </appengine-web-app> Thanks, Sagar On Thursday, November 12, 2015 at 7:24:45 AM UTC-8, Patrice (Cloud Platform Support) wrote: > > Hi again Sagar, > > There are two things that you can do (I got a bit more information because > I realized you have a case opened with Support as well). What I gathered > from the other case is twofold in what you can do, if you don't want to > switch the library: > > 1- You could reuse your connections instead of opening a new one for each > HTTP request > 2- In your code you set the read timeout and the connect timeout manually, > right? You might be better off setting these in your configuration file, as > explained here[1]. That should save you some calls to set socket options. > > Let me know if these help. I'm focusing on these since I know it can be > painful to remove the library from your code. > > Cheers > > [1] > https://cloud.google.com/appengine/docs/java/config/appconfig#url_fetch_timeout > > On Wednesday, November 11, 2015 at 2:43:05 PM UTC-5, Sagar Mutha wrote: >> >> Not a solution I wanted to hear :( But, I guess I will have to do it if >> the library is the problem maker. Is there a library/approach that GAE >> recommends? >> >> Thanks, >> Sagar >> >> On Thursday, November 5, 2015 at 11:39:30 PM UTC-8, Sagar Mutha wrote: >>> >>> I have seen this error 2 days in a row now. My app is way below the >>> quota but it keeps showing this exception. >>> `/api/seat >>> >>> com.google.apphosting.api.ApiProxy$OverQuotaException: The API call >>> remote_socket.SetSocketOptions() required more quota than is available.` >>> >>> This is adversely affecting the user experience of my app. So please help >>> me fix asap. >>> >>> App Id - saseatavailability >>> >>> -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/e44d716c-77a7-4b78-b06b-8d314478cf34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
