Hi, For me, guaranteed to be enqueued means guaranteed to be be executed as long as needed (until success) as gaej is protected against too frequent retries by the exponential backoff.
I don't find what you ask for in the docs: limit or no limit at all. So, I guess that we now need to turn to Googler to see what they say... I'll watch their answer too. regards didier On Jan 21, 4:43 pm, "ss.require" <ss.requ...@gmail.com> wrote: > I am agreed with you about these things. But in documentation I didn't > find anything that says that all needed task retries are guaranteed. > > -----------Second, about your question, tasks within transactions are > guaranteed: > ----------"You can enqueue a task as part of a datastore transaction, > such that > ---------the task is only enqueued—and guaranteed to be enqueued—if > the > ---------transaction is committed successfully." Source: > ---------http://-ode.google.com/appengine/docs/java/taskqueue/ > overview.html#Ta..., > > That says that tasks are guaranteed to be enqueued but that doesn't > say that tasks are guaranteed to be done after they have been > enqueued. E.g. Task failes 100 times and there is not a retry attempt > for 101 time -> task is undone forever. > Please, correct me if i am wrong! -- 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-java@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.
