Hi, You can also use task-retry-limit and various backoff params to adjust the retry process of your tasks
See /appengine/docs/java/config/ queue.html#Configuring_Retry_Attempts_for_Failed_Task I usually personally prefer to decide from within the task itself by using the X-AppEngine-TaskRetryCount http header. When it has reached a given value, the task stops itself and terminate. It gives you more flexibility (you can read parameter tables or do other stuff to decide) than the static parameters of queue.xml See http://code.google.com/appengine/docs/java/taskqueue/overview.html#Task_Request_Headers. regards didier On Jan 18, 10:04 pm, rishi khanna <[email protected]> wrote: > In some situations mostly when there is some App Engine Task Queue issue (it > shows status as Elevated) I see some of my queues get too big causing issues > on my real-time requests, which often, in the logs I see fail, since the > request is waiting for too long to be processed. > > I was wondering if I could have an expiry time set for the tasks in the > queue so that the tasks are not run after a given time. Should I be using > <task-age-limit> > in the queue.xml to set the expiry time? Does the task get dropped from the > queue after the expiry is reached ? -- 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.
