Hi Clay. The datastore timeout limit is fixed. If you're using transactions, you should be able to rollback your changes if any of the writes (in this case, deletes) failed. But this will only work if all entities that you're deleting are in the same entity group. Since bulk updates to entities in the same group are performed sequentially and not in parallel, you will likely see these errors consistently if you pass in the maximum of 500. You should try lowering this number until this particular exception stops being triggered consistently. - Jason
On Fri, Sep 18, 2009 at 5:04 AM, Clay Lenhart <c...@lenharts.net> wrote: > > I received an error that the commit timed out using the Java low-level > API. The transaction actually succeeded, which was unexpected. > > The operation deleted around 1000 to 2000 entities (in batches of > 500). > > The biggest issue is when the timeout occurs, we are not sure whether > the transaction will succeed or not. This uncertainty goes against one > of the reasons we'd want to use transactions (think: transfer money > from one bank account to another where one bank account is in GAE). > > Can you give us the opportunity to specify our own timeout as we'll > know what is best for our apps? Or set a larger default timeout? > > Also, can you rollback on timeout? > > Cheers, > Clay > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
