[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[Locke]

I have seen this error even for "hello world." It MAY be caused by too
many simultaneous requests, but it also may be caused by a problem
with appengine itself.

On Jan 22, 12:30 pm, Don Schwarz  wrote:
> On Fri, Jan 22, 2010 at 10:55 AM, Millisecond  wrote:
> > I'm getting this log message a lot in my application:
>
> > >>"Request was aborted after waiting too long to attempt to service your
> > request. Most likely, this indicates that you have reached your simultaneous
> > dynamic request limit. This is almost always due to excessively high latency
> > in your app. Please 
> > seehttp://code.google.com/appengine/docs/quotas.htmlformore details."
>
> > I do have "excessive latency" in that I run non-trivial tasks in the
> > TaskQueue handlers interacting with external systems averaging about
> > 10 seconds per handler with a couple per "cycle" pushing the 30 second
> > limit, but on the Dashboard my requests/second never seem to exceed
> > ~1.5.  I have billing enabled and my understanding is that gives me
> > 500 simultaneous requests.
>
> That's not accurate.  Where did you hear this?
>
> Here's the documentation we have on this:
>
> http://code.google.com/appengine/docs/java/runtime.htmlsays:
>
> *** An application can process around 30 active dynamic requests
> simultaneously. This means that an application whose average server-side
> request processing time is 75 milliseconds can serve up to (1000 ms/second /
> 75 ms/request) * 30 = 400 requests/second without incurring any additional
> latency. Applications that are heavily CPU-bound may incur some additional
> latency in long-running requests in order to make room for other apps
> sharing the same servers. Requests for static files are not affected by this
> limit.
>
> *If your application is making efficient use of resources and traffic is
> about to exceed your expected maximum queries per second, you can request
> that the simultaneous dynamic request limit be
> raised.
> App Engine can scale far beyond 30 simultaneous requests; this default limit
> is in place to prevent a poorly performing or malicious app from hoarding
> resources.*
>
> I suggest that you calculate the maximum number of simultaneous requests
> that you need to serve and fill out the above form.
>
> Thanks,
> Don

-- 
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.

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[Millisecond]

Ah, you're right, only this bit stuck in my head "quotas with billing
enabled can accommodate around 500 requests per second" from
http://code.google.com/appengine/docs/quotas.html

Thanks for the pointer to the math working that number back from the
30 request / s limit.  Seems a little optimistic though that a request
could be handled in 75ms (or faster with the -implied- math on the
quota page) with the average query latency these days being way over
that itself.  Here's hoping those come down soon.

Also thanks for the pointer to upping the limit.

-C

On Jan 22, 9:30 am, Don Schwarz  wrote:
> On Fri, Jan 22, 2010 at 10:55 AM, Millisecond  wrote:
> > I'm getting this log message a lot in my application:
>
> > >>"Request was aborted after waiting too long to attempt to service your
> > request. Most likely, this indicates that you have reached your simultaneous
> > dynamic request limit. This is almost always due to excessively high latency
> > in your app. Please 
> > seehttp://code.google.com/appengine/docs/quotas.htmlformore details."
>
> > I do have "excessive latency" in that I run non-trivial tasks in the
> > TaskQueue handlers interacting with external systems averaging about
> > 10 seconds per handler with a couple per "cycle" pushing the 30 second
> > limit, but on the Dashboard my requests/second never seem to exceed
> > ~1.5.  I have billing enabled and my understanding is that gives me
> > 500 simultaneous requests.
>
> That's not accurate.  Where did you hear this?
>
> Here's the documentation we have on this:
>
> http://code.google.com/appengine/docs/java/runtime.htmlsays:
>
> *** An application can process around 30 active dynamic requests
> simultaneously. This means that an application whose average server-side
> request processing time is 75 milliseconds can serve up to (1000 ms/second /
> 75 ms/request) * 30 = 400 requests/second without incurring any additional
> latency. Applications that are heavily CPU-bound may incur some additional
> latency in long-running requests in order to make room for other apps
> sharing the same servers. Requests for static files are not affected by this
> limit.
>
> *If your application is making efficient use of resources and traffic is
> about to exceed your expected maximum queries per second, you can request
> that the simultaneous dynamic request limit be
> raised.
> App Engine can scale far beyond 30 simultaneous requests; this default limit
> is in place to prevent a poorly performing or malicious app from hoarding
> resources.*
>
> I suggest that you calculate the maximum number of simultaneous requests
> that you need to serve and fill out the above form.
>
> Thanks,
> Don

-- 
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.

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[sdr]

I am also getting this error on a simple app that sends back "hello
world" essentially.  There does seem to be something strange going on
because I'm the only one accessing the app, so it couldn't be
simultaneous requests.  Have you found anything around this?

On Jan 22, 11:44 am, Locke  wrote:
> I have seen this error even for "hello world." It MAY be caused by too
> many simultaneous requests, but it also may be caused by a problem
> with appengine itself.
>
> On Jan 22, 12:30 pm, Don Schwarz  wrote:> On Fri, Jan 
> 22, 2010 at 10:55 AM, Millisecond  wrote:
> > > I'm getting this log message a lot in my application:
>
> > > >>"Request was aborted after waiting too long to attempt to service your
> > > request. Most likely, this indicates that you have reached your 
> > > simultaneous
> > > dynamic request limit. This is almost always due to excessively high 
> > > latency
> > > in your app. Please 
> > > seehttp://code.google.com/appengine/docs/quotas.htmlformoredetails.";
>
> > > I do have "excessive latency" in that I run non-trivial tasks in the
> > > TaskQueue handlers interacting with external systems averaging about
> > > 10 seconds per handler with a couple per "cycle" pushing the 30 second
> > > limit, but on the Dashboard my requests/second never seem to exceed
> > > ~1.5.  I have billing enabled and my understanding is that gives me
> > > 500 simultaneous requests.
>
> > That's not accurate.  Where did you hear this?
>
> > Here's the documentation we have on this:
>
> >http://code.google.com/appengine/docs/java/runtime.htmlsays:
>
> > *** An application can process around 30 active dynamic requests
> > simultaneously. This means that an application whose average server-side
> > request processing time is 75 milliseconds can serve up to (1000 ms/second /
> > 75 ms/request) * 30 = 400 requests/second without incurring any additional
> > latency. Applications that are heavily CPU-bound may incur some additional
> > latency in long-running requests in order to make room for other apps
> > sharing the same servers. Requests for static files are not affected by this
> > limit.
>
> > *If your application is making efficient use of resources and traffic is
> > about to exceed your expected maximum queries per second, you can request
> > that the simultaneous dynamic request limit be
> > raised.
> > App Engine can scale far beyond 30 simultaneous requests; this default limit
> > is in place to prevent a poorly performing or malicious app from hoarding
> > resources.*
>
> > I suggest that you calculate the maximum number of simultaneous requests
> > that you need to serve and fill out the above form.
>
> > Thanks,
> > Don

-- 
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.

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[Kroc]

Hello,
I'm developping an App (fullmetalgalaxy.com) with GWT/AppEngine and
I've got the same error in production server:
“Request was aborted after waiting too long to attempt to service your
request. Most likely, this indicates that you have reached your
simultaneous dynamic request limit. This is almost always due to
excessively high latency in your app. Please see
http://code.google.com/appengine/docs/quotas.html for more details.”

My app may be poorly designed and I'm using a long pooling technique
for server push...
nevertheless I don't understand how I can exceed 30 simultaneous
dynamic request with only few client !

I though that web browser was able to handle only 2 simultaneous
request for a single domain name, if I'm right how can I exceed 30
requests with only few clients (less than 10) ?
Is there any other way to get this error ?

I'm using http filter for a good part of my static resources (mainly
to set cache lifetime), are these requests count as dynamics request ?
If yes, do I have another way to set cache lifetime (at least for
*.nocache.* and *.cache.* patern)

My long pooling request last for 26 sec but spend most of there time
in a “Thread.sleep()”... Are sleeping request count as one for all
simultaneous request ? I guest yes, but what other choice do I have to
do server push on AppEngine ?

Apparently enabling billing let application scale to around 500
request per second... How many in simultaneous dynamic request ? If I
don't exceed free quota, will enabling billing rise the max number of
simultaneous request ?

Thanks for your attention
Vincent

-- 
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.

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[Kroc]

> I have found I usually get this error when my app is loading and takes  
> more than 10 seconds while another request come in.  Does your app  
> take longer than 10 seconds to load?

Hum yes it may be this...
But I don't know how to measure the loading time and how to reduce it.
If a remove some useless jar file ?

Vincent

-- 
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.

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request

[buzzjourney]

Hi App Engine Team,

I wanted to add more info for this issue.
My App is in Development. I am experiencing this issue when there is no 
load. (max 2 concurrent requests and I see there are 3 live instances).
Over the past 24 hours I got this error for ~8% of the requests.

This is not the first time I experience such an issue (high rate of these 
random 500 responses). 
What should I do the next time this happens?
Is there anything I can do by myself?
Should I contact the app engine team every time this happens? If I should 
contact the app engine team, what is the best way of doing that? The forum 
is hardly responsive enough for when I go live.

Please advise, 
Thanx, Lior


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine-java/-/_x-19mnW9woJ.
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.

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[Simon]

It's a loading request - please read the FAQ on what causes it and how
to minimise their occurrence at 
http://code.google.com/appengine/kb/java.html#What_Is_A_Loading_Request

On Jul 2, 11:00 am, sree  wrote:
> application id: su-raksha
> version: appengine-java-sdk-1.3.5
>
> precompilation enabled
>
> what is the reason for the below message in the log ?
>
> Request was aborted after waiting too long to attempt to service your
> request. This may happen sporadically when the App Engine serving
> cluster is under unexpectedly high or uneven load. If you see this
> message frequently, please contact the App Engine team.
>
> response will be
> Error: Server Error
>
> please explain the cause and how to solve it ?

-- 
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.

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[James]

Someone correct me if any of this is inaccurate, but:
- This occurs exactly 10s into a request.
- They are not catchable; your code doesn't even start to spin up;
there's nothing you can do about it.
- Status page - http://code.google.com/status/appengine - usually
shows all is fine when this occurs.
- These are a fact of life w/ GAE right now.

This has been my experience, at least.  Just got one on my own app
which prompted me to look around and see if there was any news on the
issue.

James





On Oct 28, 6:11 pm, Shaun Clark  wrote:
> I'm sure I'm doing something wrong, but I feel like I am getting a lot
> of these:
>
> 10-28 02:36PM 34.293 /googlesyncactions.do?action=syncemailforeveryone
> 500 10005ms 0cpu_ms 0kb AppEngine-Google; (+http://code.google.com/
> appengine)
> W 10-28 02:36PM 44.299Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:34PM 31.118 /googlesyncactions.do 500 10302ms 0cpu_ms 0kb
> AppEngine-Google; (+http://code.google.com/appengine)
> W 10-28 02:34PM 41.420Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:34PM 31.089 /googlesyncactions.do 500 10008ms 0cpu_ms 0kb
> AppEngine-Google; (+http://code.google.com/appengine)
> W 10-28 02:34PM 41.098Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:34PM 31.066 /googlesyncactions.do 500 10020ms 0cpu_ms 0kb
> AppEngine-Google; (+http://code.google.com/appengine)
> W 10-28 02:34PM 41.086Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:34PM 31.035 /googlesyncactions.do 500 10050ms 0cpu_ms 0kb
> AppEngine-Google; (+http://code.google.com/appengine)
> W 10-28 02:34PM 41.085Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:34PM 19.565 /dashboard 500 10280ms 0cpu_ms 0kb AppEngine-
> Google; (+http://code.google.com/appengine)
> W 10-28 02:34PM 29.846Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:16PM 17.637 /settingsActions.do?
> action=updateSettings&settingsjson=%7B%22key
> %22:%22aglsZXhtYXR0ZXJyGgsSEk1haW5DbGllbnRTZXR0aW5ncxja6xgM%22,%22name
> %22:%22LexMatter%22,%22url%22:%22lexmatter%22,%22paypalusername
> %22:%22shaunc869%22,%22paypalpassword
> %22:%22shaunc869%22,%22defaultbillingrate
> %22:%220.0%22,%22targetbillingsperyear%22:%22871,000%22,%22firmyearend
> %22:%2212/23/2010%22,%22paypaldepositaccount
> %22:%22aglsZXhtYXR0ZXJyEwsSC0JhbmtBY2NvdW50GKn1Ggw
> %22,%22adwordsaccountnumber%22:%22null
> %22%7D&settingskey=aglsZXhtYXR0ZXJyGgsSEk1haW5DbGllbnRTZXR0aW5ncxja6xgM
> 500 117ms 133cpu_ms 16api_cpu_ms 0kb Mozilla/5.0 (Windows; U; Windows
> NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41
> Safari/534.7,gzip(gfe),gzip(gfe)
> W 10-28 02:16PM 17.743 /settingsActions.do
> com.google.gson.JsonParseException: The JsonDeserializer
> DoubleDeserializer failed to deserialized json object "871,000" given
> the
> C 10-28 02:16PM 17.746 Uncaught exception from servlet
> com.google.gson.JsonParseException: The JsonDeserializer
> DoubleDeserializer failed to deserialized json object "871,00
> 10-28 02:09PM 54.105 /dashboard 500 10297ms 0cpu_ms 0kb AppEngine-
> Google; (+http://code.google.com/appengine)
> W 10-28 02:10PM 04.403Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:09PM 52.418 /googlesyncactions.do 500 10085ms 0cpu_ms 0kb
> AppEngine-Google; (+http://code.google.com/appengine)
> W 10-28 02:10PM 02.504Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:09PM 52.384 /googlesyncactions.do 500 10118ms 0cpu_ms 0kb
> AppEngine-Google; (+http://code.google.com/appengine)
> W 10-28 02:10PM 02.503Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:09PM 52.367 /googlesyncactions.do 500 10135ms 0cpu_ms 0kb
> AppEngine-Google; (+http://code.google.com/appengine)
> W 10-28 02:10PM 02.502Request was aborted after waiting too long toattempt to 
> service your request. This may happen sporadically when the
> App Engine serving cluster is und
> 10-28 02:09PM 52.343 /googlesyncactions.do 500 10157ms 0cpu_ms 0kb
> AppEngine-Google; (+http://code.google.com/appengine)
> W 10-28 02:10PM 02.501Request was aborted afte

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[James]

Also, pretty much EVERYONE who doesn't dislike reliability should be
starring this issue - 
http://code.google.com/p/googleappengine/issues/detail?id=2396

:p



On Nov 4, 1:25 pm, James  wrote:
> Someone correct me if any of this is inaccurate, but:
> - This occurs exactly 10s into a request.
> - They are not catchable; your code doesn't even start to spin up;
> there's nothing you can do about it.
> - Status page -http://code.google.com/status/appengine- usually
> shows all is fine when this occurs.
> - These are a fact of life w/ GAE right now.
>
> This has been my experience, at least.  Just got one on my own app
> which prompted me to look around and see if there was any news on the
> issue.
>
> James
>
> On Oct 28, 6:11 pm, Shaun Clark  wrote:
>
>
>
>
>
>
>
> > I'm sure I'm doing something wrong, but I feel like I am getting a lot
> > of these:
>
> > 10-28 02:36PM 34.293 /googlesyncactions.do?action=syncemailforeveryone
> > 500 10005ms 0cpu_ms 0kb AppEngine-Google; (+http://code.google.com/
> > appengine)
> > W 10-28 02:36PM 44.299Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:34PM 31.118 /googlesyncactions.do 500 10302ms 0cpu_ms 0kb
> > AppEngine-Google; (+http://code.google.com/appengine)
> > W 10-28 02:34PM 41.420Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:34PM 31.089 /googlesyncactions.do 500 10008ms 0cpu_ms 0kb
> > AppEngine-Google; (+http://code.google.com/appengine)
> > W 10-28 02:34PM 41.098Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:34PM 31.066 /googlesyncactions.do 500 10020ms 0cpu_ms 0kb
> > AppEngine-Google; (+http://code.google.com/appengine)
> > W 10-28 02:34PM 41.086Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:34PM 31.035 /googlesyncactions.do 500 10050ms 0cpu_ms 0kb
> > AppEngine-Google; (+http://code.google.com/appengine)
> > W 10-28 02:34PM 41.085Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:34PM 19.565 /dashboard 500 10280ms 0cpu_ms 0kb AppEngine-
> > Google; (+http://code.google.com/appengine)
> > W 10-28 02:34PM 29.846Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:16PM 17.637 /settingsActions.do?
> > action=updateSettings&settingsjson=%7B%22key
> > %22:%22aglsZXhtYXR0ZXJyGgsSEk1haW5DbGllbnRTZXR0aW5ncxja6xgM%22,%22name
> > %22:%22LexMatter%22,%22url%22:%22lexmatter%22,%22paypalusername
> > %22:%22shaunc869%22,%22paypalpassword
> > %22:%22shaunc869%22,%22defaultbillingrate
> > %22:%220.0%22,%22targetbillingsperyear%22:%22871,000%22,%22firmyearend
> > %22:%2212/23/2010%22,%22paypaldepositaccount
> > %22:%22aglsZXhtYXR0ZXJyEwsSC0JhbmtBY2NvdW50GKn1Ggw
> > %22,%22adwordsaccountnumber%22:%22null
> > %22%7D&settingskey=aglsZXhtYXR0ZXJyGgsSEk1haW5DbGllbnRTZXR0aW5ncxja6xgM
> > 500 117ms 133cpu_ms 16api_cpu_ms 0kb Mozilla/5.0 (Windows; U; Windows
> > NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41
> > Safari/534.7,gzip(gfe),gzip(gfe)
> > W 10-28 02:16PM 17.743 /settingsActions.do
> > com.google.gson.JsonParseException: The JsonDeserializer
> > DoubleDeserializer failed to deserialized json object "871,000" given
> > the
> > C 10-28 02:16PM 17.746 Uncaught exception from servlet
> > com.google.gson.JsonParseException: The JsonDeserializer
> > DoubleDeserializer failed to deserialized json object "871,00
> > 10-28 02:09PM 54.105 /dashboard 500 10297ms 0cpu_ms 0kb AppEngine-
> > Google; (+http://code.google.com/appengine)
> > W 10-28 02:10PM 04.403Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:09PM 52.418 /googlesyncactions.do 500 10085ms 0cpu_ms 0kb
> > AppEngine-Google; (+http://code.google.com/appengine)
> > W 10-28 02:10PM 02.504Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:09PM 52.384 /googlesyncactions.do 500 10118ms 0cpu_ms 0kb
> > AppEngine-Google; (+http://code.google.com/appengine)
> > W 10-28 02:10PM 02.503Request was aborted after waiting too long toattempt 
> > to service your request. This may happen sporadically when the
> > App Engine serving cluster is und
> > 10-28 02:09PM 52.367 /googlesyncactions.do 500 10135ms 0cpu_ms 0kb
> > AppEngine-Google; (+http://code.go

[appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[Fred]

I'm also experiencing this with two larger apps that use Guice and had
the suspicion it appears due to Guice start-up time.
On a smaller app that has only few bindings it does not seem to occur.
Anyone sharing this experience?

Cheers,
Fred

On Nov 4, 7:27 pm, James  wrote:
> Also, pretty much EVERYONE who doesn't dislike reliability should be
> starring this issue 
> -http://code.google.com/p/googleappengine/issues/detail?id=2396
>
> :p
>
> On Nov 4, 1:25 pm, James  wrote:
>
> > Someone correct me if any of this is inaccurate, but:
> > - This occurs exactly 10s into a request.
> > - They are not catchable; your code doesn't even start to spin up;
> > there's nothing you can do about it.
> > - Status page -http://code.google.com/status/appengine-usually
> > shows all is fine when this occurs.
> > - These are a fact of life w/ GAE right now.
>
> > This has been my experience, at least.  Just got one on my own app
> > which prompted me to look around and see if there was any news on the
> > issue.
>
> > James
>
> > On Oct 28, 6:11 pm, Shaun Clark  wrote:
>
> > > I'm sure I'm doing something wrong, but I feel like I am getting a lot
> > > of these:
>
> > > 10-28 02:36PM 34.293 /googlesyncactions.do?action=syncemailforeveryone
> > > 500 10005ms 0cpu_ms 0kb AppEngine-Google; (+http://code.google.com/
> > > appengine)
> > > W 10-28 02:36PM 44.299Request was aborted after waiting too long 
> > > toattempt to service your request. This may happen sporadically when the
> > > App Engine serving cluster is und
> > > 10-28 02:34PM 31.118 /googlesyncactions.do 500 10302ms 0cpu_ms 0kb
> > > AppEngine-Google; (+http://code.google.com/appengine)
> > > W 10-28 02:34PM 41.420Request was aborted after waiting too long 
> > > toattempt to service your request. This may happen sporadically when the
> > > App Engine serving cluster is und
> > > 10-28 02:34PM 31.089 /googlesyncactions.do 500 10008ms 0cpu_ms 0kb
> > > AppEngine-Google; (+http://code.google.com/appengine)
> > > W 10-28 02:34PM 41.098Request was aborted after waiting too long 
> > > toattempt to service your request. This may happen sporadically when the
> > > App Engine serving cluster is und
> > > 10-28 02:34PM 31.066 /googlesyncactions.do 500 10020ms 0cpu_ms 0kb
> > > AppEngine-Google; (+http://code.google.com/appengine)
> > > W 10-28 02:34PM 41.086Request was aborted after waiting too long 
> > > toattempt to service your request. This may happen sporadically when the
> > > App Engine serving cluster is und
> > > 10-28 02:34PM 31.035 /googlesyncactions.do 500 10050ms 0cpu_ms 0kb
> > > AppEngine-Google; (+http://code.google.com/appengine)
> > > W 10-28 02:34PM 41.085Request was aborted after waiting too long 
> > > toattempt to service your request. This may happen sporadically when the
> > > App Engine serving cluster is und
> > > 10-28 02:34PM 19.565 /dashboard 500 10280ms 0cpu_ms 0kb AppEngine-
> > > Google; (+http://code.google.com/appengine)
> > > W 10-28 02:34PM 29.846Request was aborted after waiting too long 
> > > toattempt to service your request. This may happen sporadically when the
> > > App Engine serving cluster is und
> > > 10-28 02:16PM 17.637 /settingsActions.do?
> > > action=updateSettings&settingsjson=%7B%22key
> > > %22:%22aglsZXhtYXR0ZXJyGgsSEk1haW5DbGllbnRTZXR0aW5ncxja6xgM%22,%22name
> > > %22:%22LexMatter%22,%22url%22:%22lexmatter%22,%22paypalusername
> > > %22:%22shaunc869%22,%22paypalpassword
> > > %22:%22shaunc869%22,%22defaultbillingrate
> > > %22:%220.0%22,%22targetbillingsperyear%22:%22871,000%22,%22firmyearend
> > > %22:%2212/23/2010%22,%22paypaldepositaccount
> > > %22:%22aglsZXhtYXR0ZXJyEwsSC0JhbmtBY2NvdW50GKn1Ggw
> > > %22,%22adwordsaccountnumber%22:%22null
> > > %22%7D&settingskey=aglsZXhtYXR0ZXJyGgsSEk1haW5DbGllbnRTZXR0aW5ncxja6xgM
> > > 500 117ms 133cpu_ms 16api_cpu_ms 0kb Mozilla/5.0 (Windows; U; Windows
> > > NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41
> > > Safari/534.7,gzip(gfe),gzip(gfe)
> > > W 10-28 02:16PM 17.743 /settingsActions.do
> > > com.google.gson.JsonParseException: The JsonDeserializer
> > > DoubleDeserializer failed to deserialized json object "871,000" given
> > > the
> > > C 10-28 02:16PM 17.746 Uncaught exception from servlet
> > > com.google.gson.JsonParseException: The JsonDeserializer
> > > DoubleDeserializer failed to deserialized json object "871,00
> > > 10-28 02:09PM 54.105 /dashboard 500 10297ms 0cpu_ms 0kb AppEngine-
> > > Google; (+http://code.google.com/appengine)
> > > W 10-28 02:10PM 04.403Request was aborted after waiting too long 
> > > toattempt to service your request. This may happen sporadically when the
> > > App Engine serving cluster is und
> > > 10-28 02:09PM 52.418 /googlesyncactions.do 500 10085ms 0cpu_ms 0kb
> > > AppEngine-Google; (+http://code.google.com/appengine)
> > > W 10-28 02:10PM 02.504Request was aborted after waiting too long 
> > > toattempt to service your request. This may happen sporadically when the
> > > App Engine serving cluster is un

Re: [appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[John Patterson]

On 3 Mar 2010, at 00:22, Kroc wrote:


Hello,
I'm developping an App (fullmetalgalaxy.com) with GWT/AppEngine and
I've got the same error in production server:
“Request was aborted after waiting too long to attempt to service your
request. Most likely, this indicates that you have reached your
simultaneous dynamic request limit. This is almost always due to
excessively high latency in your app. Please see
http://code.google.com/appengine/docs/quotas.html for more details.”


I have found I usually get this error when my app is loading and takes  
more than 10 seconds while another request come in.  Does your app  
take longer than 10 seconds to load?



My app may be poorly designed and I'm using a long pooling technique
for server push...
nevertheless I don't understand how I can exceed 30 simultaneous
dynamic request with only few client !

I though that web browser was able to handle only 2 simultaneous
request for a single domain name, if I'm right how can I exceed 30
requests with only few clients (less than 10) ?
Is there any other way to get this error ?

I'm using http filter for a good part of my static resources (mainly
to set cache lifetime), are these requests count as dynamics request ?
If yes, do I have another way to set cache lifetime (at least for
*.nocache.* and *.cache.* patern)


Set static resources and cache times in your appengine-web.xml.  That  
way Google serves them directly without hitting your app.




My long pooling request last for 26 sec but spend most of there time
in a “Thread.sleep()”... Are sleeping request count as one for all
simultaneous request ? I guest yes, but what other choice do I have to
do server push on AppEngine ?


I think there is no good solution on App Engine for server push.   
Polling would be the only option because as you say, simultaneous  
requests are limited.



Apparently enabling billing let application scale to around 500
request per second... How many in simultaneous dynamic request ? If I
don't exceed free quota, will enabling billing rise the max number of
simultaneous request ?


Its still 30 unless you get permission.


Thanks for your attention
Vincent

--
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-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.

Re: [appengine-java] Re: Request was aborted after waiting too long to attempt to service your request.

[Don Schwarz]

Here's some good advice:

http://googleappengine.blogspot.com/2009/12/request-performance-in-java.html

On Tue, Mar 2, 2010 at 5:41 PM, Kroc  wrote:

>
> > I have found I usually get this error when my app is loading and takes
> > more than 10 seconds while another request come in.  Does your app
> > take longer than 10 seconds to load?
>
> Hum yes it may be this...
> But I don't know how to measure the loading time and how to reduce it.
> If a remove some useless jar file ?
>
> Vincent
>
> --
> 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.
>
>

-- 
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.

Re: [appengine-java] Re: Request was aborted after waiting too long to attempt to service your request

[cakowundu]

W
Sent from my BlackBerry® smartphone provided by Airtel Nigeria.

-Original Message-
From: buzzjourney 
Sender: google-appengine-java@googlegroups.com
Date: Sun, 11 Dec 2011 22:21:27 
To: 
Reply-To: google-appengine-java@googlegroups.com
Subject: [appengine-java] Re: Request was aborted after waiting too long to
 attempt to service your request

Hi App Engine Team,

I wanted to add more info for this issue.
My App is in Development. I am experiencing this issue when there is no 
load. (max 2 concurrent requests and I see there are 3 live instances).
Over the past 24 hours I got this error for ~8% of the requests.

This is not the first time I experience such an issue (high rate of these 
random 500 responses). 
What should I do the next time this happens?
Is there anything I can do by myself?
Should I contact the app engine team every time this happens? If I should 
contact the app engine team, what is the best way of doing that? The forum 
is hardly responsive enough for when I go live.

Please advise, 
Thanx, Lior


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine-java/-/_x-19mnW9woJ.
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.

Re: [appengine-java] Re: Request was aborted after waiting too long to attempt to service your request

[kwanja9999]

Sent from my BlackBerry® by dtac.

-Original Message-
From: cakowu...@gmail.com
Sender: google-appengine-java@googlegroups.com
Date: Mon, 12 Dec 2011 07:58:59 
To: 
Reply-To: google-appengine-java@googlegroups.com
Subject: Re: [appengine-java] Re: Request was aborted after waiting too long
 to attempt to service your request

W
Sent from my BlackBerry® smartphone provided by Airtel Nigeria.

-Original Message-
From: buzzjourney 
Sender: google-appengine-java@googlegroups.com
Date: Sun, 11 Dec 2011 22:21:27 
To: 
Reply-To: google-appengine-java@googlegroups.com
Subject: [appengine-java] Re: Request was aborted after waiting too long to
 attempt to service your request

Hi App Engine Team,

I wanted to add more info for this issue.
My App is in Development. I am experiencing this issue when there is no 
load. (max 2 concurrent requests and I see there are 3 live instances).
Over the past 24 hours I got this error for ~8% of the requests.

This is not the first time I experience such an issue (high rate of these 
random 500 responses). 
What should I do the next time this happens?
Is there anything I can do by myself?
Should I contact the app engine team every time this happens? If I should 
contact the app engine team, what is the best way of doing that? The forum 
is hardly responsive enough for when I go live.

Please advise, 
Thanx, Lior


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine-java/-/_x-19mnW9woJ.
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.


-- 
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.

Re: [appengine-java] Re: Request was aborted after waiting too long to attempt to service your request

[kwanja9999]

Sent from my BlackBerry® by dtac.

-Original Message-
From: kwanja9...@yahoo.com
Date: Mon, 12 Dec 2011 09:16:01 
To: 
Reply-To: kwanja9...@yahoo.com
Subject: Re: [appengine-java] Re: Request was aborted after waiting too long to 
attempt to service your request


Sent from my BlackBerry® by dtac.

-Original Message-
From: cakowu...@gmail.com
Sender: google-appengine-java@googlegroups.com
Date: Mon, 12 Dec 2011 07:58:59 
To: 
Reply-To: google-appengine-java@googlegroups.com
Subject: Re: [appengine-java] Re: Request was aborted after waiting too long
 to attempt to service your request

W
Sent from my BlackBerry® smartphone provided by Airtel Nigeria.

-Original Message-
From: buzzjourney 
Sender: google-appengine-java@googlegroups.com
Date: Sun, 11 Dec 2011 22:21:27 
To: 
Reply-To: google-appengine-java@googlegroups.com
Subject: [appengine-java] Re: Request was aborted after waiting too long to
 attempt to service your request

Hi App Engine Team,

I wanted to add more info for this issue.
My App is in Development. I am experiencing this issue when there is no 
load. (max 2 concurrent requests and I see there are 3 live instances).
Over the past 24 hours I got this error for ~8% of the requests.

This is not the first time I experience such an issue (high rate of these 
random 500 responses). 
What should I do the next time this happens?
Is there anything I can do by myself?
Should I contact the app engine team every time this happens? If I should 
contact the app engine team, what is the best way of doing that? The forum 
is hardly responsive enough for when I go live.

Please advise, 
Thanx, Lior


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine-java/-/_x-19mnW9woJ.
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.


-- 
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.