[hmm, this
question<http://stackoverflow.com/questions/9331545/which-task-queue-exceptions-raised-from-add-make-sense-to-retry>didn't
attract any interest on StackOverflow..., thought I'd give it a try
here]

I'm looking to add some defensive exception handling/retry logic around my
(Java) code that enqueues tasks in App Engine. In reviewing the
documentation for potential exceptions raised, I see several candidates
that might make sense to catch and handle with a retry, but the
documentation is a bit vague, so I thought I'd see what others have found
to be worthwhile.

Here are the ones I'm looking at, and their descriptions from the docs:

- InternalFailureException - Internal task queue error.
- TransientFailureException - Intermittent failure.
- QueueFailureException - Unspecified queue failure.
- TransactionalTaskException - Queue operation failure caused by
Datastore exception.

The only one for which the docs explicitly suggest that retrying might be
helpful is TransientFailureException.

Also, regarding TransactionalTaskException, is this something that would
only arise when enlisting a task in an enclosing datastore transaction, or
could this arise when enqueuing a standalone task?

--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/JV4cR4o2BNYJ.
To post to this group, send email to google-appengine@xxxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to
google-appengine+unsubscribe@xxxxxxxxxxxxxxxxx
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.