 remote.shutdown() does not kill an akka remote actor itself
By : user3244951
Date : March 29 2020, 07:55 AM
it should still fix some issue An actor can kill itself by invoking self.stop. So forget the PoisonPill and just use the Stop message: code :
case "Stop" => {
println("stopping...")
self.stop
remote.shutdown()
}
|
 Akka.Remote - cannot send messages to remote actor after dissassociation
By : TwelveMonkeys
Date : March 29 2020, 07:55 AM
it fixes the issue [ INFO] 2016-01-21 13:04:58.6550 Quarantined address [akka.tcp://qb@client:8090] is still unreachable or has not been restarted. Keeping it quarantined. - that says it all. The node was quarantined which requires a restart of the actor system.
However, IMHO - just upgrade to Akka.NET 1.0.6, which we released on Monday. We made the remoting policy manager much less brittle than it has been historically.
|
akka sending a closure to remote actor + Error in sending messages (case class) between Scala Akka remote actors
By : Hyeong-Hun Kim
Date : March 29 2020, 07:55 AM
Does that help The key thing here is that you have defined two different protocols for each actor:
Common object that resides in the RemoteActor.scala file Common object that resides in the LocalActor.scala file
|
Akka Actor can't connect to remote server where Scala Actor could
By : Ezal Isa
Date : March 29 2020, 07:55 AM
should help you out DISCLAIMER: I am the PO of Akka
Try using a raw IP address instead of a hostname in remote.start(), if that doesn't solve it you have 2 options:
|
Akka Actor: Remote actor exception "Futures timed out after"
By : Miłosz Nycz
Date : March 29 2020, 07:55 AM
Any of those help For solving above problem, we need to follow two steps that are metnion below:
|
code :
Related Posts :