Interface AskSupport
-
Method Summary
Modifier and TypeMethodDescriptionImport this implicit conversion to gain?
andask
methods onpekko.actor.ActorRef
, which will defer to theask(actorRef, message)(timeout)
method defined here.scala.concurrent.Future<Object>
scala.concurrent.Future<Object>
Sends a message asynchronously and returns aFuture
holding the eventual reply message; this means that the target actor needs to send the result to thesender
reference provided.ask
(ActorSelection actorSelection) Import this implicit conversion to gain?
andask
methods onpekko.actor.ActorSelection
, which will defer to theask(actorSelection, message)(timeout)
method defined here.scala.concurrent.Future<Object>
ask
(ActorSelection actorSelection, Object message, ActorRef sender, Timeout timeout) scala.concurrent.Future<Object>
ask
(ActorSelection actorSelection, Object message, Timeout timeout) Sends a message asynchronously and returns aFuture
holding the eventual reply message; this means that the target actor needs to send the result to thesender
reference provided.scala.concurrent.Future<Object>
askWithStatus
(ActorRef actorRef, Object message, ActorRef sender, Timeout timeout) Use for messages whose response is known to be apekko.pattern.StatusReply
.scala.concurrent.Future<Object>
askWithStatus
(ActorRef actorRef, Object message, Timeout timeout) Use for messages whose response is known to be apekko.pattern.StatusReply
.
-
Method Details
-
ask
Import this implicit conversion to gain?
andask
methods onpekko.actor.ActorRef
, which will defer to theask(actorRef, message)(timeout)
method defined here.import org.apache.pekko.pattern.ask val future = actor ? message // => ask(actor, message) val future = actor ask message // => ask(actor, message) val future = actor.ask(message)(timeout) // => ask(actor, message)(timeout)
All of the above use an implicit
pekko.util.Timeout
. -
ask
Sends a message asynchronously and returns aFuture
holding the eventual reply message; this means that the target actor needs to send the result to thesender
reference provided.The Future will be completed with an
pekko.pattern.AskTimeoutException
after the given timeout has expired; this is independent from any timeout applied while awaiting a result for this future (i.e. inAwait.result(..., timeout)
). A typical reason forAskTimeoutException
is that the recipient actor didn't send a reply.Warning: When using future callbacks, inside actors you need to carefully avoid closing over the containing actor’s object, i.e. do not call methods or access mutable state on the enclosing actor from within the callback. This would break the actor encapsulation and may introduce synchronization bugs and race conditions because the callback will be scheduled concurrently to the enclosing actor. Unfortunately there is not yet a way to detect these illegal accesses at compile time.
Recommended usage:
val f = ask(worker, request)(timeout) f.map { response => EnrichedMessage(response) } pipeTo nextActor
-
ask
-
ask
Import this implicit conversion to gain?
andask
methods onpekko.actor.ActorSelection
, which will defer to theask(actorSelection, message)(timeout)
method defined here.import org.apache.pekko.pattern.ask val future = selection ? message // => ask(selection, message) val future = selection ask message // => ask(selection, message) val future = selection.ask(message)(timeout) // => ask(selection, message)(timeout)
All of the above use an implicit
pekko.util.Timeout
. -
ask
Sends a message asynchronously and returns aFuture
holding the eventual reply message; this means that the target actor needs to send the result to thesender
reference provided.The Future will be completed with an
pekko.pattern.AskTimeoutException
after the given timeout has expired; this is independent from any timeout applied while awaiting a result for this future (i.e. inAwait.result(..., timeout)
). A typical reason forAskTimeoutException
is that the recipient actor didn't send a reply.Warning: When using future callbacks, inside actors you need to carefully avoid closing over the containing actor’s object, i.e. do not call methods or access mutable state on the enclosing actor from within the callback. This would break the actor encapsulation and may introduce synchronization bugs and race conditions because the callback will be scheduled concurrently to the enclosing actor. Unfortunately there is not yet a way to detect these illegal accesses at compile time.
Recommended usage:
val f = ask(worker, request)(timeout) f.map { response => EnrichedMessage(response) } pipeTo nextActor
-
ask
scala.concurrent.Future<Object> ask(ActorSelection actorSelection, Object message, ActorRef sender, Timeout timeout) -
askWithStatus
Use for messages whose response is known to be apekko.pattern.StatusReply
. When apekko.pattern.StatusReply.Success
response arrives the future is completed with the wrapped value, if apekko.pattern.StatusReply.Error
arrives the future is instead failed. -
askWithStatus
scala.concurrent.Future<Object> askWithStatus(ActorRef actorRef, Object message, ActorRef sender, Timeout timeout) Use for messages whose response is known to be apekko.pattern.StatusReply
. When apekko.pattern.StatusReply.Success
response arrives the future is completed with the wrapped value, if apekko.pattern.StatusReply.Error
arrives the future is instead failed.
-