Categories: Stamps

Akka Documentation

Published by

Join Lenon Blur

1 year ago

For the full documentation of this feature and for new projects see mailboxes.

You might be interested in

Dependency

The Akka dependencies are available from Akka’s library repository. To access them there, you need to configure the URL for this repository.

You are watching: Akka Documentation

sbtresolvers += “Akka library repository”.at(“https://repo.akka.io/maven”) Maven<project&gt … <repositories> <repository> <id>akka-repository</id> <name>Akka library repository</name> <url>https://repo.akka.io/maven</url> </repository> </repositories&gt </project> Gradlerepositories { mavenCentral() maven { url “https://repo.akka.io/maven” } }

To use Mailboxes, you must add the following dependency in your project:

sbtval AkkaVersion = “2.8.5” libraryDependencies += “com.typesafe.akka” %% “akka-actor” % AkkaVersionMaven<properties> <scala.binary.version>2.13</scala.binary.version> </properties> <dependencyManagement> <dependencies> <dependency> <groupId>com.typesafe.akka</groupId> <artifactId>akka-bom_${scala.binary.version}</artifactId> <version>2.8.5</version> <type>pom</type> <scope>import</scope> </dependency&gt </dependencies> </dependencyManagement> <dependencies&gt <dependency> <groupId>com.typesafe.akka</groupId> <artifactId>akka-actor_${scala.binary.version}</artifactId> </dependency&gt </dependencies>Gradledef versions = [ ScalaBinary: “2.13” ] dependencies { implementation platform(“com.typesafe.akka:akka-bom_${versions.ScalaBinary}:2.8.5”) implementation “com.typesafe.akka:akka-actor_${versions.ScalaBinary}” }

Introduction

An Akka Mailbox holds the messages that are destined for an ActorActor. Normally each Actor has its own mailbox, but with for example a BalancingPoolBalancingPool all routees will share a single mailbox instance.

For more details on advanced mailbox config and custom mailbox implementations, see Mailboxes.

Mailbox Selection

Default Mailbox

The default mailbox is used when the mailbox is not specified. This is an unbounded mailbox, backed by a java.util.concurrent.ConcurrentLinkedQueue.

SingleConsumerOnlyUnboundedMailboxSingleConsumerOnlyUnboundedMailbox is an even more efficient mailbox, and it can be used as the default mailbox, but it cannot be used with a BalancingDispatcher.

Configuration of SingleConsumerOnlyUnboundedMailbox as default mailbox:

akka.actor.default-mailbox { mailbox-type = “akka.dispatch.SingleConsumerOnlyUnboundedMailbox” }

Requiring a Message Queue Type for an Actor

It is possible to require a certain type of message queue for a certain type of actor by having that actor extendimplement the parameterized traitinterface RequiresMessageQueueRequiresMessageQueue. Here is an example:

Scala copysourceimport akka.dispatch.RequiresMessageQueue import akka.dispatch.BoundedMessageQueueSemantics class MyBoundedActor extends MyActor with RequiresMessageQueue[BoundedMessageQueueSemantics] Java copysourceimport akka.dispatch.BoundedMessageQueueSemantics; import akka.dispatch.RequiresMessageQueue; public class MyBoundedActor extends MyActor implements RequiresMessageQueue<BoundedMessageQueueSemantics> {}

The type parameter to the RequiresMessageQueue traitinterface needs to be mapped to a mailbox in configuration like this:

Requiring a Message Queue Type for a Dispatcher

A dispatcher may also have a requirement for the mailbox type used by the actors running on it. An example is the BalancingDispatcher which requires a message queue that is thread-safe for multiple concurrent consumers. Such a requirement is formulated within the dispatcher configuration section:

my-dispatcher { mailbox-requirement = org.example.MyInterface }

The given requirement names a class or interface which will then be ensured to be a supertype of the message queue’s implementation. In case of a conflict—e.g. if the actor requires a mailbox type which does not satisfy this requirement—then actor creation will fail.

How the Mailbox Type is Selected

When an actor is created, the ActorRefProviderActorRefProvider first determines the dispatcher which will execute it. Then the mailbox is determined as follows:

If the actor’s deployment configuration section contains a mailbox key, this refers to a configuration section describing the mailbox type.
If the actor’s PropsProps contains a mailbox selection then that names a configuration section describing the mailbox type to be used. This needs to be an absolute config path, for example myapp.special-mailbox, and is not nested inside the akka namespace.
If the dispatcher’s configuration section contains a mailbox-type key the same section will be used to configure the mailbox type.
If the actor requires a mailbox type as described above then the mapping for that requirement will be used to determine the mailbox type to be used; if that fails then the dispatcher’s requirement—if any—will be tried instead.
If the dispatcher requires a mailbox type as described above then the mapping for that requirement will be used to determine the mailbox type to be used.
The default mailbox akka.actor.default-mailbox will be used.

Mailbox configuration examples

PriorityMailbox

How to create a PriorityMailbox:

Scala copysourceimport akka.dispatch.PriorityGenerator import akka.dispatch.UnboundedStablePriorityMailbox import com.typesafe.config.Config // We inherit, in this case, from UnboundedStablePriorityMailbox // and seed it with the priority generator class MyPrioMailbox(settings: ActorSystem.Settings, config: Config) extends UnboundedStablePriorityMailbox( // Create a new PriorityGenerator, lower prio means more important PriorityGenerator { // highpriority messages should be treated first if possible case “highpriority” => 0 // lowpriority messages should be treated last if possible case “lowpriority” => 2 // PoisonPill when no other left case PoisonPill => 3 // We default to 1, which is in between high and low case otherwise => 1 }) Java copysourcestatic class MyPrioMailbox extends UnboundedStablePriorityMailbox { // needed for reflective instantiation public MyPrioMailbox(ActorSystem.Settings settings, Config config) { // Create a new PriorityGenerator, lower prio means more important super( new PriorityGenerator() { @Override public int gen(Object message) { if (message.equals(“highpriority”)) return 0; // ‘highpriority messages should be treated first if possible else if (message.equals(“lowpriority”)) return 2; // ‘lowpriority messages should be treated last if possible else if (message.equals(PoisonPill.getInstance())) return 3; // PoisonPill when no other left else return 1; // By default they go between high and low prio } }); } }

And then add it to the configuration:

copysourceprio-dispatcher { mailbox-type = “docs.dispatcher.DispatcherDocSpec$MyPrioMailbox” //Other dispatcher configuration goes here }

And then an example on how you would use it:

Scala copysource// We create a new Actor that just prints out what it processes class Logger extends Actor { val log: LoggingAdapter = Logging(context.system, this) self ! “lowpriority” self ! “lowpriority” self ! “highpriority” self ! “pigdog” self ! “pigdog2” self ! “pigdog3” self ! “highpriority” self ! PoisonPill def receive = { case x => log.info(x.toString) } } val a = system.actorOf(Props(classOf[Logger], this).withDispatcher(“prio-dispatcher”)) /* * Logs: * highpriority * highpriority * pigdog * pigdog2 * pigdog3 * lowpriority * lowpriority */ Java copysourceclass Demo extends AbstractActor { LoggingAdapter log = Logging.getLogger(getContext().getSystem(), this); { for (Object msg : new Object[] { “lowpriority”, “lowpriority”, “highpriority”, “pigdog”, “pigdog2”, “pigdog3”, “highpriority”, PoisonPill.getInstance() }) { getSelf().tell(msg, getSelf()); } } @Override public Receive createReceive() { return receiveBuilder() .matchAny( message -> { log.info(message.toString()); }) .build(); } } // We create a new Actor that just prints out what it processes ActorRef myActor = system.actorOf(Props.create(Demo.class, this).withDispatcher(“prio-dispatcher”)); /* Logs: ‘highpriority ‘highpriority ‘pigdog ‘pigdog2 ‘pigdog3 ‘lowpriority ‘lowpriority */

It is also possible to configure a mailbox type directly like this (this is a top-level configuration entry):

Scala copysourceprio-mailbox { mailbox-type = “docs.dispatcher.DispatcherDocSpec$MyPrioMailbox” //Other mailbox configuration goes here } akka.actor.deployment { /priomailboxactor { mailbox = prio-mailbox } } Java copysourceprio-mailbox { mailbox-type = “docs.dispatcher.DispatcherDocSpec$MyPrioMailbox” //Other mailbox configuration goes here } akka.actor.deployment { /priomailboxactor { mailbox = prio-mailbox } }

And then use it either from deployment like this:

Scala copysourceimport akka.actor.Props val myActor = context.actorOf(Props[MyActor](), “priomailboxactor”) Java copysourceActorRef myActor = system.actorOf(Props.create(MyActor.class), “priomailboxactor”);

Or code like this:

Scala copysourceimport akka.actor.Props val myActor = context.actorOf(Props[MyActor]().withMailbox(“prio-mailbox”)) Java copysourceActorRef myActor = system.actorOf(Props.create(MyActor.class).withMailbox(“prio-mailbox”));

ControlAwareMailbox

A ControlAwareMailbox can be very useful if an actor needs to be able to receive control messages immediately no matter how many other messages are already in its mailbox.

It can be configured like this:

copysourcecontrol-aware-dispatcher { mailbox-type = “akka.dispatch.UnboundedControlAwareMailbox” //Other dispatcher configuration goes here }

Control messages need to extend the ControlMessageControlMessage traitinterface:

Scala copysourceimport akka.dispatch.ControlMessage case object MyControlMessage extends ControlMessage Java copysourcestatic class MyControlMessage implements ControlMessage {}

And then an example on how you would use it:

Scala copysource// We create a new Actor that just prints out what it processes class Logger extends Actor { val log: LoggingAdapter = Logging(context.system, this) self ! “foo” self ! “bar” self ! MyControlMessage self ! PoisonPill def receive = { case x => log.info(x.toString) } } val a = system.actorOf(Props(classOf[Logger], this).withDispatcher(“control-aware-dispatcher”)) /* * Logs: * MyControlMessage * foo * bar */ Java copysourceclass Demo extends AbstractActor { LoggingAdapter log = Logging.getLogger(getContext().getSystem(), this); { for (Object msg : new Object[] {“foo”, “bar”, new MyControlMessage(), PoisonPill.getInstance()}) { getSelf().tell(msg, getSelf()); } } @Override public Receive createReceive() { return receiveBuilder() .matchAny( message -> { log.info(message.toString()); }) .build(); } } // We create a new Actor that just prints out what it processes ActorRef myActor = system.actorOf(Props.create(Demo.class, this).withDispatcher(“control-aware-dispatcher”)); /* Logs: ‘MyControlMessage ‘foo ‘bar */

Special Semantics of system.actorOf

In order to make system.actorOfsystem.actorOf both synchronous and non-blocking while keeping the return type ActorRefActorRef (and the semantics that the returned ref is fully functional), special handling takes place for this case. Behind the scenes, a hollow kind of actor reference is constructed, which is sent to the system’s guardian actor who actually creates the actor and its context and puts those inside the reference. Until that has happened, messages sent to the ActorRefActorRef will be queued locally, and only upon swapping the real filling in will they be transferred into the real mailbox. Thus,

Scala val props: Props = … // this actor uses MyCustomMailbox, which is assumed to be a singleton system.actorOf(props.withDispatcher(“myCustomMailbox”)) ! “bang” assert(MyCustomMailbox.instance.getLastEnqueuedMessage == “bang”) Java final Props props = … // this actor uses MyCustomMailbox, which is assumed to be a singleton system.actorOf(props.withDispatcher(“myCustomMailbox”).tell(“bang”, sender); assert(MyCustomMailbox.getInstance().getLastEnqueued().equals(“bang”));

will probably fail; you will have to allow for some time to pass and retry the check à la TestKit.awaitCondTestKit.awaitCond.

Source: https://antiquewolrd.com
Categories: Stamps

Join Lenon Blur

I am a JOIN LENON BLUR - world-leading expert, and I am the admin of Antiqueworld with many years of experience researching antiques and postal publications. I hope to provide the audience with the most accurate and informative information.