When remote actor's JVM is killed via ^C, watchers (on different JVMs) do not get Terminated Messages.
They get: Association with remote system [akka.tcp://blah@127.0.0.1:2553] has failed, address is now gated for [5000] ms. Reason is: [Disassociated]. I know that they get Terminated messages if the actor dies without JVM being killed. Here is my scenario: I have an actor (A) that has path to actor (B). Both live on different jvms. Actor A sends an identity requests, gets the actor ref, and watches it. Then I kill jvm shell that B runs on. Actor (A) never gets a Terminated message. I don't think it matters but actor A is spawned within Play 2.3.1 Is this normal behaviour? How can A detect that B, or B's jvm is down and start looking for it periodically so that it can reconnect when B is running again? Thanks. -- >>>>>>>>>> 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.
