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

[buzzjourney]

Hi App Engine Team,

I've started getting random 500 responses with  "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."

This is not under load. 

My app id is "buzzjourney".
Please assist.

-- 
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/-/16iF-eX5Ji4J.
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] Request was aborted after waiting too long to attempt to service your request.

[Ikai Lan (Google)]

Yeah, that can potentially set things off, but I think you'll be fine.. If
the ratio is low, you will probably be okay, though. I'm saying this because
one way people have "cheated" the system if they had lots of slow requests
was by making lots and lots of essentially no-op requests via the task queue
to average out the latency such that they would be autoassigned more
instances. I'm not sure how we've dealt with that - if at all - but you have
a similar phenomenon, albeit as a result of a perfectly legitimate usage.

As a thought - what about sending something to a special task queue that
only handles these types of requests and returning that data to the client
via the Channel API?

I wish there were some way to make the Facebook JavaScript API play nicely
with server-side requests. I'm not aware of any at the moment.

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 Wed, Jun 8, 2011 at 5:39 PM, Jeff Schnitzer  wrote:

> Sorry, when I said "I have a GWT app that takes one major hit at
> startup (possibly seconds)" I meant the GWT client app itself, on
> startup, has a login() call to the server that can take seconds to
> process.  Synchronizing facebook data and all that jazz.
>
> I'm not terribly concerned about this since the ratio of login()s to
> "other queries" is low, browser refreshes will find mostly cached
> data, and I am now hitting Facebook with multiple batches in
> parallel... but since I don't really know the limits, it would suck to
> find out my architecture doesn't work in-vivo.
>
> Jeff
>
> On Wed, Jun 8, 2011 at 1:50 AM, Ikai Lan (Google) 
> wrote:
> > IIRC, the loading request latency doesn't affect the average time. It's
> an
> > average, I believe, and it's a moving window.
> > A long startup time, however, will result in the scheduler almost always
> > favoring putting items in the pending queue instead of spinning up new
> > instances, though. When scheduling a request, we do the lesser of:
> > cold start time vs. sliding window of pending ms
> > So if your app takes 10 seconds to startup and requests are spending 5
> > seconds in the pending queue, we will send the requests to the pending
> queue
> > until the expected wait is 10+ seconds. If we decide to spin up new
> > instances, we only spin up one instance at a time. During the spin up
> time,
> > we continue to place new requests on the queue.
> > I'm thinking we need a new section about scheduling, auto scaling and
> > wallclock. The wallclock stuff is probably the most confusing ...
> > 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 Wed, Jun 8, 2011 at 1:50 PM, Jeff Schnitzer 
> wrote:
> >>
> >> Is this documented anywhere?  It's something I figured out from
> >> occasional comments I've seen on this list over the years, but I've
> >> never seen it mentioned in the official documentation.  And it's kinda
> >> important.
> >>
> >> In particular, I'd like to know what the bounds are for threaded java,
> >> and how the average time is computed - is it mean, median, or mode?  I
> >> have a GWT app that takes one major hit at startup (possibly seconds)
> >> and then performs lots of smaller hits as the user interacts with the
> >> app.  It would be nice to know if this will cause problems down the
> >> road...
> >>
> >> Jeff
> >>
> >> On Tue, Jun 7, 2011 at 6:41 PM, Ikai Lan (Google) 
> >> wrote:
> >> > You get this error when your request waits in a pending queue.
> >> > App Engine apps are autoscaled IF they can average under 1000ms. If
> they
> >> > cannot, we do not give you additional instances, and requests line up
> in
> >> > a
> >> > pending queue. If your request waits in the pending queue for more
> than
> >> > N
> >> > seconds (I think N is 9 at the moment but I don't know for sure off
> the
> >> > top
> >> > of my head), this message is returned.
> >> > You'll need to look at the average latency and figure out how to drop
> it
> >> > to
> >> > under 1000ms. Alternatively, if you enable concurrent Java requests,
> >> > it'll
> >> > be a higher ceiling before this error appears if you have "Always On"
> >> > since
> >> > you can serve a total of 3 (always on instances) * M (concurrency
> >> > factor, I
> >> > think this is 40 at the moment) requests at one time without requiring
> >> > autoscaling.
> >> > 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 Wed, Jun 8, 2011 at 1:06 AM, holger 
> >> > wrote:
> >> >>
> >> >> Hello everyone,
> >> >>
> >> >>
> >> >> i am running a java REST service in the appengine and get this:
> >> >>
> >> >> "Reques

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

[Jeff Schnitzer]

Sorry, when I said "I have a GWT app that takes one major hit at
startup (possibly seconds)" I meant the GWT client app itself, on
startup, has a login() call to the server that can take seconds to
process.  Synchronizing facebook data and all that jazz.

I'm not terribly concerned about this since the ratio of login()s to
"other queries" is low, browser refreshes will find mostly cached
data, and I am now hitting Facebook with multiple batches in
parallel... but since I don't really know the limits, it would suck to
find out my architecture doesn't work in-vivo.

Jeff

On Wed, Jun 8, 2011 at 1:50 AM, Ikai Lan (Google)  wrote:
> IIRC, the loading request latency doesn't affect the average time. It's an
> average, I believe, and it's a moving window.
> A long startup time, however, will result in the scheduler almost always
> favoring putting items in the pending queue instead of spinning up new
> instances, though. When scheduling a request, we do the lesser of:
> cold start time vs. sliding window of pending ms
> So if your app takes 10 seconds to startup and requests are spending 5
> seconds in the pending queue, we will send the requests to the pending queue
> until the expected wait is 10+ seconds. If we decide to spin up new
> instances, we only spin up one instance at a time. During the spin up time,
> we continue to place new requests on the queue.
> I'm thinking we need a new section about scheduling, auto scaling and
> wallclock. The wallclock stuff is probably the most confusing ...
> 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 Wed, Jun 8, 2011 at 1:50 PM, Jeff Schnitzer  wrote:
>>
>> Is this documented anywhere?  It's something I figured out from
>> occasional comments I've seen on this list over the years, but I've
>> never seen it mentioned in the official documentation.  And it's kinda
>> important.
>>
>> In particular, I'd like to know what the bounds are for threaded java,
>> and how the average time is computed - is it mean, median, or mode?  I
>> have a GWT app that takes one major hit at startup (possibly seconds)
>> and then performs lots of smaller hits as the user interacts with the
>> app.  It would be nice to know if this will cause problems down the
>> road...
>>
>> Jeff
>>
>> On Tue, Jun 7, 2011 at 6:41 PM, Ikai Lan (Google) 
>> wrote:
>> > You get this error when your request waits in a pending queue.
>> > App Engine apps are autoscaled IF they can average under 1000ms. If they
>> > cannot, we do not give you additional instances, and requests line up in
>> > a
>> > pending queue. If your request waits in the pending queue for more than
>> > N
>> > seconds (I think N is 9 at the moment but I don't know for sure off the
>> > top
>> > of my head), this message is returned.
>> > You'll need to look at the average latency and figure out how to drop it
>> > to
>> > under 1000ms. Alternatively, if you enable concurrent Java requests,
>> > it'll
>> > be a higher ceiling before this error appears if you have "Always On"
>> > since
>> > you can serve a total of 3 (always on instances) * M (concurrency
>> > factor, I
>> > think this is 40 at the moment) requests at one time without requiring
>> > autoscaling.
>> > 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 Wed, Jun 8, 2011 at 1:06 AM, holger 
>> > wrote:
>> >>
>> >> Hello everyone,
>> >>
>> >>
>> >> i am running a java REST service in the appengine and get this:
>> >>
>> >> "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."
>> >>
>> >>
>> >> I see this message frequently and customer requests fail because of it.
>> >> Can anyone help me please! Thanks a lot.
>> >>
>> >> --
>> >> 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/-/X3E4cnhhblA3Z3dK.
>> >> 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 gr

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

[Ikai Lan (Google)]

IIRC, the loading request latency doesn't affect the average time. It's an
average, I believe, and it's a moving window.

A long startup time, however, will result in the scheduler almost always
favoring putting items in the pending queue instead of spinning up new
instances, though. When scheduling a request, we do the lesser of:

cold start time vs. sliding window of pending ms

So if your app takes 10 seconds to startup and requests are spending 5
seconds in the pending queue, we will send the requests to the pending queue
until the expected wait is 10+ seconds. If we decide to spin up new
instances, we only spin up one instance at a time. During the spin up time,
we continue to place new requests on the queue.

I'm thinking we need a new section about scheduling, auto scaling and
wallclock. The wallclock stuff is probably the most confusing ...

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 Wed, Jun 8, 2011 at 1:50 PM, Jeff Schnitzer  wrote:

> Is this documented anywhere?  It's something I figured out from
> occasional comments I've seen on this list over the years, but I've
> never seen it mentioned in the official documentation.  And it's kinda
> important.
>
> In particular, I'd like to know what the bounds are for threaded java,
> and how the average time is computed - is it mean, median, or mode?  I
> have a GWT app that takes one major hit at startup (possibly seconds)
> and then performs lots of smaller hits as the user interacts with the
> app.  It would be nice to know if this will cause problems down the
> road...
>
> Jeff
>
> On Tue, Jun 7, 2011 at 6:41 PM, Ikai Lan (Google) 
> wrote:
> > You get this error when your request waits in a pending queue.
> > App Engine apps are autoscaled IF they can average under 1000ms. If they
> > cannot, we do not give you additional instances, and requests line up in
> a
> > pending queue. If your request waits in the pending queue for more than N
> > seconds (I think N is 9 at the moment but I don't know for sure off the
> top
> > of my head), this message is returned.
> > You'll need to look at the average latency and figure out how to drop it
> to
> > under 1000ms. Alternatively, if you enable concurrent Java requests,
> it'll
> > be a higher ceiling before this error appears if you have "Always On"
> since
> > you can serve a total of 3 (always on instances) * M (concurrency factor,
> I
> > think this is 40 at the moment) requests at one time without requiring
> > autoscaling.
> > 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 Wed, Jun 8, 2011 at 1:06 AM, holger 
> wrote:
> >>
> >> Hello everyone,
> >>
> >>
> >> i am running a java REST service in the appengine and get this:
> >>
> >> "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."
> >>
> >>
> >> I see this message frequently and customer requests fail because of it.
> >> Can anyone help me please! Thanks a lot.
> >>
> >> --
> >> 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/-/X3E4cnhhblA3Z3dK.
> >> 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.
>
>

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

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

[Jeff Schnitzer]

Is this documented anywhere?  It's something I figured out from
occasional comments I've seen on this list over the years, but I've
never seen it mentioned in the official documentation.  And it's kinda
important.

In particular, I'd like to know what the bounds are for threaded java,
and how the average time is computed - is it mean, median, or mode?  I
have a GWT app that takes one major hit at startup (possibly seconds)
and then performs lots of smaller hits as the user interacts with the
app.  It would be nice to know if this will cause problems down the
road...

Jeff

On Tue, Jun 7, 2011 at 6:41 PM, Ikai Lan (Google)  wrote:
> You get this error when your request waits in a pending queue.
> App Engine apps are autoscaled IF they can average under 1000ms. If they
> cannot, we do not give you additional instances, and requests line up in a
> pending queue. If your request waits in the pending queue for more than N
> seconds (I think N is 9 at the moment but I don't know for sure off the top
> of my head), this message is returned.
> You'll need to look at the average latency and figure out how to drop it to
> under 1000ms. Alternatively, if you enable concurrent Java requests, it'll
> be a higher ceiling before this error appears if you have "Always On" since
> you can serve a total of 3 (always on instances) * M (concurrency factor, I
> think this is 40 at the moment) requests at one time without requiring
> autoscaling.
> 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 Wed, Jun 8, 2011 at 1:06 AM, holger  wrote:
>>
>> Hello everyone,
>>
>>
>> i am running a java REST service in the appengine and get this:
>>
>> "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."
>>
>>
>> I see this message frequently and customer requests fail because of it.
>> Can anyone help me please! Thanks a lot.
>>
>> --
>> 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/-/X3E4cnhhblA3Z3dK.
>> 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] Request was aborted after waiting too long to attempt to service your request.

[Holger Weissböck]

Hello Ikai,

thanks a lot for clearing that up! I will test my app with concurrent
threads and try it. This was on my todo list anyway. ;-)

However, the funny thing is that its latency averages at about 150ms. If i
am not able to figure it out, i'll be back here.

Thanks again,
Holger

On Wed, Jun 8, 2011 at 3:41 AM, Ikai Lan (Google)  wrote:

> You get this error when your request waits in a pending queue.
>
> App Engine apps are autoscaled IF they can average under 1000ms. If they
> cannot, we do not give you additional instances, and requests line up in a
> pending queue. If your request waits in the pending queue for more than N
> seconds (I think N is 9 at the moment but I don't know for sure off the top
> of my head), this message is returned.
>
> You'll need to look at the average latency and figure out how to drop it to
> under 1000ms. Alternatively, if you enable concurrent Java requests, it'll
> be a higher ceiling before this error appears if you have "Always On" since
> you can serve a total of 3 (always on instances) * M (concurrency factor, I
> think this is 40 at the moment) requests at one time without requiring
> autoscaling.
>
> 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 Wed, Jun 8, 2011 at 1:06 AM, holger wrote:
>
>> Hello everyone,
>>
>>
>> i am running a java REST service in the appengine and get this:
>>
>> "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."
>>
>>
>> I see this message frequently and customer requests fail because of it. Can 
>> anyone help me please! Thanks a lot.
>>
>>  --
>> 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/-/X3E4cnhhblA3Z3dK.
>> 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.
>



-- 
Holger Weissböck
hol...@gamua.com
http://gamua.com
http://www.sparrow-framework.org

-- 
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] Request was aborted after waiting too long to attempt to service your request.

[Ikai Lan (Google)]

You get this error when your request waits in a pending queue.

App Engine apps are autoscaled IF they can average under 1000ms. If they
cannot, we do not give you additional instances, and requests line up in a
pending queue. If your request waits in the pending queue for more than N
seconds (I think N is 9 at the moment but I don't know for sure off the top
of my head), this message is returned.

You'll need to look at the average latency and figure out how to drop it to
under 1000ms. Alternatively, if you enable concurrent Java requests, it'll
be a higher ceiling before this error appears if you have "Always On" since
you can serve a total of 3 (always on instances) * M (concurrency factor, I
think this is 40 at the moment) requests at one time without requiring
autoscaling.

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 Wed, Jun 8, 2011 at 1:06 AM, holger  wrote:

>
> Hello everyone,
>
>
>
> i am running a java REST service in the appengine and get this:
>
>
> "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."
>
>
>
> I see this message frequently and customer requests fail because of it. Can 
> anyone help me please! Thanks a lot.
>
>  --
> 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/-/X3E4cnhhblA3Z3dK.
> 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.

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

[holger]

Hello everyone,


i am running a java REST service in the appengine and get this:

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


I see this message frequently and customer requests fail because of it. Can 
anyone help me please! Thanks a lot.

-- 
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/-/X3E4cnhhblA3Z3dK.
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] Request was aborted after waiting too long to attempt to service your request.

[Shaun Clark]

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.299 Request was aborted after waiting too long to
attempt 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.420 Request was aborted after waiting too long to
attempt 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.098 Request was aborted after waiting too long to
attempt 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.086 Request was aborted after waiting too long to
attempt 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.085 Request was aborted after waiting too long to
attempt 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.846 Request was aborted after waiting too long to
attempt 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.403 Request was aborted after waiting too long to
attempt 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.504 Request was aborted after waiting too long to
attempt 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.503 Request was aborted after waiting too long to
attempt 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.502 Request was aborted after waiting too long to
attempt 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.501 Request was aborted after waiting too long to
attempt to service your request. This may happen sporadically when the
App Engine serving cluster is und
10-28 02:08PM 37.024 /googlesyncactions.do?action=syncemailforeveryone
500 10051ms 0cpu_ms 0kb AppEngine-Google; (+http://code.google.com/
appengine)
W 10-28 02:08PM 47.076 Request was aborted after waiting too long to
attempt to service your request. This may happen sporadically when the
App Engine serving cluster is und
10-28 02:07PM 26.899 /dashboard 500 10068ms 0cpu_ms 0kb AppEngine-
Google; (+http://code.google.com/appengine)
W 10-28 02:07PM 36.968 Request was aborted after waiting too long to
attempt to service your request. This may happen sporadic

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

[sree]

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] Request was aborted after waiting too long to attempt to service your request.

[Anupam]

I often see the following message in my application logs:

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

Also our application is currently under development.

We get this message for a few of our requests:
"This request used a high amount of CPU and will soon exceed its
quota"

What is it suppose to mean? The latency for these requests is very
high (about 12000 ms) however we have assigned a large quota for our
application(100 $ / day) when my application still generally runs
under its free quota.

We are working on the optimization of our application. However our
algorithms would still require a large amount of CPU.

Please let me know how we could resolve these issues,
Any help is appreciated.

Thanks.

-- 
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] Request was aborted after waiting too long to attempt to service your request

[Terry]

These days, the logs show these warnings frequently and get the
response code 500:
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.

Each request will cause my app to fetch about 10 small web pages, but
it will complete in 30 seconds. A few days ago, it worked fine, but
now almost all these requests will get 500 from server.
Please Help!

-- 
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] Request was aborted after waiting too long to attempt to service your request: Request queued for less than 30 seconds

[Wong]

I get "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." when
there is another request coming in meanwhile my application is being
initialized after it is spin-down.

My application takes around 26 seconds to start-up. During this 26
seconds, if there is another request, the request will hit the
"Request was aborted after waiting too long to attempt to service your
request" error in 2-10 seconds (before the 30s limit). If the system
can queue the request for 30s (the hard limit), I believe the request
can still be served.

The first request which triggers the application start-up was finally
served without any problem. However, the second request hits 500 error
before the first request being served. This can be observed in the
log.

04-25 07:13PM 53.849 /post/0 200 27069ms 38750cpu_ms 444api_cpu_ms 9kb
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/
20100315 Firefox/3.5.9,gzip(gfe)
  See details


I 04-25 07:13PM 57.570

  javax.servlet.ServletContext log: Initializing Spring root
WebApplicationContext

...
  W 04-25 07:14PM 20.916

  This request caused a new process to be started for your
application, and thus caused your application code to be loaded for
the first time. This request may thus take longer and use more CPU
than a typical request for your application.



 04-25 07:14PM 09.687 /person/location 500 10022ms 0cpu_ms 0kb Mozilla/
5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100315
Firefox/3.5.9,gzip(gfe)
  See details

  W 04-25 07:14PM 19.709

  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.


In this case, could the "background servers" solve the problem? How
can I hand off the request which is coming in when the application is
in the midst of starting up to the background worker?

-- 
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] Request was aborted after waiting too long to attempt to service your request.

[Don Schwarz]

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 see http://code.google.com/appengine/docs/quotas.htmlfor 
> more 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.html says:

*** 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] Request was aborted after waiting too long to attempt to service your request.

[Millisecond]

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 see http://code.google.com/appengine/docs/quotas.html for 
>>more 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.  Which if all of my TaskQueues were
executing at once I don't think I'd reach, although it might get
close.  But wouldn't that show on the dashboard?

Is there anything else that could be causing this?  I see the
DataStore has been in Anomoly for the past few days, but nobody seems
worried about it and assume roughly this latency will be "normal".

Thanks,
-C

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