Hi, I've experienced the same phenomenon so that I added a new issue for this:
http://code.google.com/p/googleappengine/issues/detail?id=2924 Thanks, Kaz On Feb 26, 8:05 am, Jerome <jerome.mou...@gmail.com> wrote: > Hello, > > We have been using task queues for a few months without problem. We > handle actions that must execute right away. > > At the time of the release of 1.3.1, we noticed that sometimes, some > tasks will take 1 to 2 minutes to start, but in the task queue, the > ETA shows as a date in the past (like 0:01:12 ago), usually 1 second > or so after the creation time. > > This is not a consistent issue. I might works perfectly (task being > kicked in within 1 second of creation) for several times and suddenly, > the next task takes 1.5 minutes to get started. > > Our task queue is empty when we see this issue. > Our queue is setup with a max rate of 5/s and a bucket size of 1. > > Any idea of what we can do to work around or solve this new issue? > > Jerome -- 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.
