To be honest, I don't know the answer but you can easily check what child actor receives. Just log every message child actor receives and see if comes any message that would indiciate that parent got killed.
Buy according to docs <http://doc.akka.io/docs/akka/2.3.4/scala/actors.html#Restart_Hooks> by default it should terminate all childrens. If you haven't overriden preRestart() method I imagine that it depends on way you kill parent actor. W dniu wtorek, 29 lipca 2014 15:07:06 UTC+2 użytkownik Sean Zhong napisał: > > 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.
