Hi Robert, Wrapper is pretty simple and at the end there is core gae task-queue api. I have had plan to create issue with core api sample, but now when I created my own ConcurrentModificationException retry request wrapper, and now for me this problem only creates additional cpu cost for every retry (up to 5 retries) I have little incentive. But I should probably make it, because maybe there is some issue that gae team doesn't know.
There are absolutely no datastore operations. I have created my own simple tasks to test this issue. My initial web request starts 4 times same task non transactionaly. This task only inserts two new tasks transactionaly, nothing else. And these two new tasks per every initial task do nothing. So in this situation with 4 tasks that only tries to insert transactionaly 2 new simple tasks, there was always contention problem at second or third transactional insert and ConcurrentModificationException was thrown. Matija. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
