You've not given the code for what ever inserts task1, or the task it inserts. So the isse could be in several spots. But from your code, if task1 happens to run twice, either due to a failure or because it decided to run twice, then you get two of the "/anothertask" tasks running. If anothertask also inserts a task... Then you've got a setup with potential problems.
Robert On Jun 18, 2011, at 5:38, BarrenTeam <[email protected]> wrote: > Thanks for the answers. I already know the mechanism for avoid bomb fork. > > But my question is: WHY and HOW can task's bomb fork happen in the code above? > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/SgzC1m1qMmAJ. > 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. -- 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.
