Any news about this strange ConcurrentModificationException ? Half year 
later I have noticed again this exception and when I started to analyze what 
happened I have found that this problem still exists. 

Two concurrent exceptions later, idempotent tasks and everything is ok, but 
can some googler explain what can cause this ? Is there some task enqueue 
limit per task queue or some infrastructural GAE scarce task queue resource 
so that we can design app to avoid this rare situation?

-- 
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.

Reply via email to