Home/ Questions/Q 3437180
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T08:02:01+00:00

In Scala, an actor can be notified when another (remote) actor terminates by setting

  • 0

In Scala, an actor can be notified when another (remote) actor terminates by setting the trapExit flag and invoking the link() method with the second actor as parameter. In this case when the remote actor ends its job by calling exit() the first one is notified by receiving an Exit message.

But what happens when the remote actor terminates in a less graceful way (e.g. the VM where it is running crashes)? In other words, how the local actor can discover that the remote one is no longer available? Of course I would prefer (if possible) that the local actor could be notified by a message similar to the Exit one, but it seems not feasible. Am I missing something? Should I continuously polling the state of the remote actor (and in this case I don’t know which is the best way to do that) or is there a smarter solution?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    But what happens when the remote actor terminates in a less graceful way (e.g. the VM where it is running crashes)

    Actor proxy stays alive accepting messages (and loosing them), and waiting for you to restart the JVM with remote actor. Watching for JVM crashes (and other failures happening on the infrastructure level) is far beyond Scala responsibilities. Good choice for that could be monitoring through JMX.

    In other words, how the local actor can discover that the remote one is no longer available?

    You may define a timeout interval (say 5000 millis). If remote actor doesn’t reply during this interval, it’s a sign for you that something unexpected is happening to remote actor, and you may either ask it about its state or just treat it as dead.

    Should I continuously polling the state of the remote actor (and in this case I don’t know which is the best way to do that) or is there a smarter solution?

    You may put a kind of a polling load balancer/dispatcher in front of a group of actors, that will use only those actors that are alive and ready to process messages (which makes sense in case of remote actors that may suddenly appear/disappear behind the proxy) -> Can Scala actors process multiple messages simultaneously?

    • 0