Oh and may I just add I am not using the datastore in any way. On Thursday, 17 October 2013 12:36:01 UTC+11, Ezequiel Muns wrote: > > I'm experiencing something similar here, tasks are dispatched to a backend > module. The backend instance displays the call to /_ah/start and then the > task is shown as 'running' (in the Task Queue section of the console). The > logs don't show any evidence that the task is running. > > If I manually invoke another call to the same backend instance, even to a > different callback, the task 'returns' and the log is shown as expected but > with a very large processing time (equivalent to the time between when the > task was scheduled to run and me manually invoking the callback). Checking > appstats shows that the task actually run in the time I expected (< 1s), it > seems that the backend just got stuck after the handler finished. > > Subsequent calls to the same instance do not exhibit the same behaviour, > only fresh instances. > > On Tuesday, 15 October 2013 11:00:09 UTC+11, Vinny P wrote: >> >> On Sun, Oct 13, 2013 at 11:48 AM, Luis Pereira <l.pereira...@gmail.com> >> wrote: >>> >>> Haven't had the chance to download the log files yet. But in the >>> console, there is no sign at all about these tasks in the backend log >>> files. Only when we shut down the backend we see those commented errors. >>> >> >> >> Backends flush log data on a periodic basis, see >> https://developers.google.com/appengine/docs/java/backends/#Java_Periodic_logging >> for >> documentation. If you're not seeing any logs, try forcibly flushing logs by >> calling ApiProxy's flushLogs() method: >> https://developers.google.com/appengine/docs/java/javadoc/com/google/apphosting/api/ApiProxy >> >> >> What's odd is that there should still be logs of the request, even if the >> application itself is not printing any log data. Hopefully the missing logs >> will be recorded in the downloadable logs service. >> >> >> On Sun, Oct 13, 2013 at 11:48 AM, Luis Pereira <l.pereira...@gmail.com> >> wrote: >> >>> We are moving to HRD in the coming weeks. Hope the issue disappears >>> after the migration. >>> >> >> >> The HRD migration is the best chance to fix this problem - M/S has >> unusual issues, and it wouldn't surprise me at all if that was the problem. >> >> >> ----------------- >> -Vinny P >> Technology & Media Advisor >> Chicago, IL >> >> App Engine Code Samples: http://www.learntogoogleit.com >> >> >
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
