Hi,
FYI: 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 for one user who is using the application and
On Wed, Dec 11, 2013 at 2:33 AM, Ananthakrishnan Venkatasubramanian
ananthakrishnan.venkatasubraman...@a-cti.com wrote:
Libraries will increase the size of the application or the parent module
if you opt for modules. Deploying the app with libraries is old
fashion...Its not good to follow if
On Tue, Dec 10, 2013 at 2:52 AM, Ananthakrishnan Venkatasubramanian
ananthakrishnan.venkatasubraman...@a-cti.com 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
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
Hi,
We are a Premier Account User in GoogleAppEngine. We have two front-end
servers running on Google AppEngine developed using Java.
Front-end server A communicates with another front-end server B using
URLFetch(java.net) request.
We have set the maximum connectionTimeOut and readTimeOuts
On Mon, Dec 9, 2013 at 10:57 AM, Ananthakrishnan Venkatasubramanian
ananthakrishnan.venkatasubraman...@a-cti.com wrote:
Can we please know why the request from Server A timeouts out without a
request being received at the other server end (ie) Server B?
There are multiple possible reasons
