Test case: parent actor: in a local machine, child actor, in a remote machine. child actor is created by parent actor by akka remote deployment.
Behavior observed: when the parent JVM is killed, the child actor is *NOT* stopped. I have not use child context.watch(parent) for this case. I oringally thought when the parent actor *cannot* connected, the child actor should *suicide itself.* Is this expected? I use akka 2.2.3 Sean -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
