Hi Bek, Two concurrent transactions on the same entity would not be enough on its own to cause this exception: If the two conflict, one of them will get in first, and the other will be failed and automatically retry. It should take substantially higher contention to cause this. As I mentioned, though, it's possible this is happening due to timeouts. With what frequency do you see this particular error?
As far as retrying goes, if this is real contention, you'd be best to tell the client to come back later, since retrying will just increase contention further. If it's due to timeouts and other external factors, though, retrying would be preferable. -Nick Johnson --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
