I can confirm this exact behavior. Except that my cron jobs run every
hour. The request fails just above 10 seconds.

On Oct 14, 6:33 pm, RollingCircle <[email protected]> wrote:
> Still occurring as of 15:30 UTC 14-OCT-09.
>
> Any ideas?
>
> On Oct 13, 3:15 pm, RollingCircle <[email protected]> wrote:
>
>
>
> > (Apologies if this appears to be a cross-posting - I did raise this as
> > a reply to a post describing a similar issue, but that reply seems to
> > have disappeared into the ether)
>
> > Since approx 21:00 UTC yesterday (12-OCT-09) my application (tag
> > 'metutil') has been suffering from roughly 75% timeouts on a
> > previously reliable cron job - although when run manually, the request
> > run by the cron job still completes correctly in all cases.
>
> > The timeout report in the log states:
>
> > "Request was aborted after waiting too long to attempt to service your
> > request. Most likely, this indicates that you have reached your
> > simultaneous active request limit. This is almost always due to
> > excessively high latency in your app. Please 
> > seehttp://code.google.com/appengine/docs/quotas.htmlformore details."
>
> > and the reported time for the request when it fails is usually just
> > over 10 seconds.  Normally, the request (which calls out via HTTP to
> > an external service) completes in a couple of seconds at most.  The
> > cron job is set to run every 15 minutes, and as noted above, currently
> > roughly every 3 out of four requests are now timing out.
>
> > Could this be related to the 1.2.6 release I've seen mentioned on
> > other threads?
>
> > Regards,
>
> > Ed

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to