Thread.sleep inside Scala actors

scala concurrency actor
As As picture As As · Sep 11, 2014 · Viewed 11.6k times · Source

Is it correct to use Thread.sleep(5000); inside an actor? Does it actualy make an actor sleep for 5 seconds? Is there a simple alternative to make an actor sleep for some seconds?

Answer

Chris K picture Chris K · Sep 11, 2014

Anything that blocks a thread is not advised within Akka. If the Actor is configured with a a shared thread pool (default behavior) then using Thread.sleep will withhold a thread from that pool that could be doing work for other Actors.

If one really must block, then an actor may be configured to have its own thread. This can be done by configuring a custom dispatcher for the actor to use, the full details are here.

The recognized alternative to blocking is to schedule a callback to the actor via a timer, for example send a message after 5 seconds.. 

akkaSystem.scheduler.scheduleOnce(5 seconds, actor, "msgFoo")

The Akka scheduler is documented here: http://doc.akka.io/docs/akka/2.3.6/scala/scheduler.html

Related questions

How do I get hold of exceptions thrown in a Scala Future?

I've been working up my answer to Is there a standard Scala function for running a block with a timeout?, and have run into a problem if an exception is thrown in a Future. def runWithTimeout[T](timeoutMs: Long)(f: =&…

Read More
Blocking calls in Akka Actors

As a newbie, I am trying to understand how actors work. And, from the documentation, I think I understand that actors are objects which gets executed in sync mode and also that actor execution can contain blocking/sync method calls, …

Read More
Scala final vs val for concurrency visibility

In Java, when using an object across multiple threads (and in general), it is good practice to make fields final. For example, public class ShareMe { private final MyObject obj; public ShareMe(MyObject obj) { this.obj = obj; } } In this case, the …

Read More