Any news way adding task to queue in transaction can throw ConcurrentModificationException ?
Does this means that you 'lock' somehow whole queue in this operation ? On Oct 21, 5:18 pm, Matija <matija.jerko...@gmail.com> wrote: > Hi, > I am > usinghttp://code.google.com/appengine/docs/java/taskqueue/overview.html#Ta... > way to enqueue two tasks in transaction. But I am not saving any > datastore entities. I am using objectify. > > I got this message: > > java.util.ConcurrentModificationException: too much contention on > these datastore entities. please try again. > at > com.google.appengine.api.datastore.DatastoreApiHelper.translateError(Datast > oreApiHelper.java: > 39) > at > com.google.appengine.api.datastore.DatastoreApiHelper.makeSyncCall(Datastor > eApiHelper.java: > 75) > at > com.google.appengine.api.datastore.TransactionImpl.makeSyncCall(Transaction > Impl.java: > 44) > at > com.google.appengine.api.datastore.TransactionImpl.makeSyncCall(Transaction > Impl.java: > 52) > at > com.google.appengine.api.datastore.TransactionImpl.commit(TransactionImpl.j > ava: > 64) > > When this happened only one task needed to be added to queue, so why > this error ? -- 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-appeng...@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.
