Hi, Definitely Server A is not exceeding the per minute quota for URLFetch API Calls (32,000 calls per min). SocketTimeOutExceptions are coming even there is less traffic in both the Servers.
Note: We have idle instances in both the servers Definitely there is no question of queueing the requests also. Requests should be served at any point of time. As far as AppStats is concerned, we already knew how to do it. Its a matter of enabling. We will enable it and give you the information about it in private. As you have suggested, we deployed the Server B as backend module and Server A as frontend module in the same App ID and used URLFetch in module A(Server A) to communicate with module B (Server B) of the same app. Still the same problem. Those exceptions are repeating. The only thing we need to test now with modules is cut down the URLFetch in module A(Server A) and communicate directly with module B(Server B). Technically we need to integrate the codebase of Server B inside module A(Server A). This we can do it and try out from our end. But my question is, imagine there are two different organisation using AppEngine and one of the sever in the organisation running in AppEngine needs to communicate with the server in the other organisation running same in AppEngine, they have to communicate with URLFetch calls only. We cannot force the organisations to create one common App and use modules to avoid SocketTimeOutExceptions. Can you please give the appropriate reasons/solutions for the same? Please let me know if you need any other information regarding this. Thanks. Regards, Anantha Krishnan. On Wednesday, December 11, 2013 10:24:14 AM UTC+5:30, Vinny P wrote: > > On Tue, Dec 10, 2013 at 2:52 AM, Ananthakrishnan Venkatasubramanian < > ananthakrishnan.venkatasubraman...@a-cti.com <javascript:>> wrote: > >> Server A & B represent different application IDs and the error rate >> depends on traffic. >> >> > > Most likely you are hitting App Engine per-minute rate limits then. Your > traffic goes up, which leads to increased requests between your AB servers, > which causes App Engine throttling to kick in to protect resource usage. > > The best way to fix this is to consolidate your applications; instead of > running applications A and B, run them within a single application ID as > separate versions or as different modules, then communicate intra-app using > task queues and other methods. Longer-term, the even better option would be > to refactor your application code so shared services are available as > libraries and not as individual endpoints. > > > On Tue, Dec 10, 2013 at 2:52 AM, Ananthakrishnan Venkatasubramanian < > ananthakrishnan.venkatasubraman...@a-cti.com <javascript:>> wrote: > >> We don't have appstats available at the moment. >> >> > > Why not? Install it using the guide available at: > https://developers.google.com/appengine/docs/java/tools/appstats > > > ----------------- > -Vinny P > Technology & Media Advisor > Chicago, IL > > App Engine Code Samples: http://www.learntogoogleit.com > > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
