--
>>>>>>>>>> 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+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
I am still interested in knowing if there is a way for the system1 application to be notified of the akka.remote.ShutDownAssociation event so that it can trigger some cleanup after losing the remote actor. Looking at the log, all the information needed is there but how can I access it?
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscribe@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
override def preStart: Unit =
{
super.preStart()
context.system.eventStream.subscribe(self, classOf[akka.remote.DisassociatedEvent])
}
Then I just had to add and entry for DisassociatedEvent in receive to trigger the behavior I wanted
override def receive =
{
case event: akka.remote.DisassociatedEvent => {
???
override def preStart(): Unit = context.system.eventStream.subscribe(self, classOf[DisassociatedEvent])
override def unhandled(message: Any): Unit = message match {
case DisassociatedEvent(local, remote, _) =>
log.info(s"Forked executor system $remote disassociated from $local ...")
case x => super.unhandled(x)
}
--
*****************************************************************************************************
** New discussion forum: https://discuss.akka.io/ replacing akka-user google-group soon.
** This group will soon be put into read-only mode, and replaced by discuss.akka.io
** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced
*****************************************************************************************************