How does the supervisor deal with congestion? Lets say that Actor A sends all it's incoming messages to child Actor B. And lets say we pass 1000 messages to actor A, then actor B will eventually also get 1000 messages. But if B for some reason throws, e.g. on each message, then actor B will throw a 1000 times unless stopped.
This is where the supervisor should come in and save us, but if the overhead of throwing an exception takes longer than passing 1000 messages to actor A. Then actor B will not be able to notify it's parent that it has thrown before actor A has processed all of the initial 1000 messages. Thus, actor B will throw 1000 times because the parent is bussy processing those initial messages. Is this the expected behavior in Akka? Or is supervision done w/o passing messages back to the owner? I assume stopping/removing/restarting children needs to be done in the parent actors context and therefore use messaging to notify the parent? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
