Hey, I think that the :
ERROR: akka.remote.transport.Transport$InvalidAssociationException: The
remote system terminated the association because it is shutting down.
should not exist in case of graceful remote system shutdown. Imagine that
you have a system that is forking JVMs with remote actor system
for each task or job (the remote actor system serves only as a way of
passing input and result) and you're getting thousands of these ERRORs,
then somebody uses your software and he gets thousands of these errors.
Btw this is nice David, unfortunately it doesn't solve the ERROR logging
problem.
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)
}
Anybody has an idea how to avoid these ERROR log messages ?
--
>>>>>>>>>> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
