I'm having the same problems, it started to occur after the 1.2.8 release, still the same with 1.3.0. Adding another cronjob 1 minute prior to the real one just to load the app...
//Peter On Dec 17, 12:18 pm, jd <[email protected]> wrote: > If your cron job has to wait longer than 10 seconds while your app is > reloading you will get this message. Do you also see a "loading > request" in the logs just after or before this error message? If so > then it is interesting that despite your 1 minute "ping", engine is > still swapping out your app. > > On Dec 16, 10:04 pm, Fabrizio <[email protected]> wrote: > > > > > Hello, > > > I have a cron job (1/m). I get many random errors like: > > 12-16 06:43AM 34.115 /"myurl......" 500 10020ms 0cpu_ms 0kb > > "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." > > > I think it's not caused by "simultaneous dynamic request limit". I > > make only 1 request/minute. > > I also noticed an high time (more than 10000ms). > > > When it works, the log is like this: > > 12-16 06:48AM 20.059 /"myurl......." 200 156ms 191cpu_ms > > 95api_cpu_ms 0kb > > > Why some requests work and other crash? I don't change anything > > between them. > > > Fabrizio -- 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 [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-java?hl=en.
