You are viewing the documentation for the new actor APIs, to view the Akka Classic documentation, see Classic Mailboxes.


Mailboxes are part of core Akka, which means that they are part of the akka-actor dependency. This page describes how to use mailboxes with akka-actor-typed, which has dependency:

val AkkaVersion = "2.6.21"
libraryDependencies += "com.typesafe.akka" %% "akka-actor-typed" % AkkaVersion
def versions = [
  ScalaBinary: "2.13"
dependencies {
  implementation platform("com.typesafe.akka:akka-bom_${versions.ScalaBinary}:2.6.21")

  implementation "com.typesafe.akka:akka-actor-typed_${versions.ScalaBinary}"


Each actor in Akka has a Mailbox, this is where the messages are enqueued before being processed by the actor.

By default an unbounded mailbox is used, this means any number of messages can be enqueued into the mailbox.

The unbounded mailbox is a convenient default but in a scenario where messages are added to the mailbox faster than the actor can process them, this can lead to the application running out of memory. For this reason a bounded mailbox can be specified, the bounded mailbox will pass new messages to deadletters when the mailbox is full.

For advanced use cases it is also possible to defer mailbox selection to config by pointing to a config path.

Selecting what mailbox is used

Selecting a Mailbox Type for an Actor

To select a specific mailbox for an actor use MailboxSelectorMailboxSelector to create a PropsProps instance for spawning your actor:

sourcecontext.spawn(childBehavior, "bounded-mailbox-child", MailboxSelector.bounded(100))

val props = MailboxSelector.fromConfig("")
context.spawn(childBehavior, "from-config-mailbox-child", props)
sourcecontext.spawn(childBehavior, "bounded-mailbox-child", MailboxSelector.bounded(100));


fromConfigfromConfig takes an absolute config path to a block defining the dispatcher in the config file:

sourcemy-app {
  my-special-mailbox {
    mailbox-type = "akka.dispatch.SingleConsumerOnlyUnboundedMailbox"

Default Mailbox

The default mailbox is used when the mailbox is not specified and is the SingleConsumerOnlyUnboundedMailboxSingleConsumerOnlyUnboundedMailbox

Which Configuration is passed to the Mailbox Type

Each mailbox type is implemented by a class which extends MailboxTypeMailboxType and takes two constructor arguments: a ActorSystem.SettingsActorSystem.Settings object and a Config section. The latter is computed by obtaining the named configuration section from the ActorSystemActorSystem configuration, overriding its id key with the configuration path of the mailbox type and adding a fall-back to the default mailbox configuration section.

Mailbox Implementations

Akka ships with a number of mailbox implementations:

Other bounded mailbox implementations which will block the sender if the capacity is reached and configured with non-zero mailbox-push-timeout-time.


The following mailboxes should only be used with zero mailbox-push-timeout-time.

Custom Mailbox type

The best way to show how to create your own Mailbox type is by example:

source// Marker trait used for mailbox requirements mapping
trait MyUnboundedMessageQueueSemantics
source// Marker interface used for mailbox requirements mapping
public interface MyUnboundedMessageQueueSemantics {}
import akka.dispatch.Envelope
import akka.dispatch.MailboxType
import akka.dispatch.MessageQueue
import akka.dispatch.ProducesMessageQueue
import com.typesafe.config.Config
import java.util.concurrent.ConcurrentLinkedQueue
import scala.Option

object MyUnboundedMailbox {
  // This is the MessageQueue implementation
  class MyMessageQueue extends MessageQueue with MyUnboundedMessageQueueSemantics {

    private final val queue = new ConcurrentLinkedQueue[Envelope]()

    // these should be implemented; queue used as example
    def enqueue(receiver: ActorRef, handle: Envelope): Unit =
    def dequeue(): Envelope = queue.poll()
    def numberOfMessages: Int = queue.size
    def hasMessages: Boolean = !queue.isEmpty
    def cleanUp(owner: ActorRef, deadLetters: MessageQueue): Unit = {
      while (hasMessages) {
        deadLetters.enqueue(owner, dequeue())

// This is the Mailbox implementation
class MyUnboundedMailbox extends MailboxType with ProducesMessageQueue[MyUnboundedMailbox.MyMessageQueue] {

  import MyUnboundedMailbox._

  // This constructor signature must exist, it will be called by Akka
  def this(settings: ActorSystem.Settings, config: Config) = {
    // put your initialization code here

  // The create method is called to create the MessageQueue
  final override def create(owner: Option[ActorRef], system: Option[ActorSystem]): MessageQueue =
    new MyMessageQueue()
import akka.dispatch.Envelope;
import akka.dispatch.MailboxType;
import akka.dispatch.MessageQueue;
import akka.dispatch.ProducesMessageQueue;
import com.typesafe.config.Config;
import java.util.concurrent.ConcurrentLinkedQueue;
import java.util.Queue;
import scala.Option;

public class MyUnboundedMailbox
    implements MailboxType, ProducesMessageQueue<MyUnboundedMailbox.MyMessageQueue> {

  // This is the MessageQueue implementation
  public static class MyMessageQueue implements MessageQueue, MyUnboundedMessageQueueSemantics {
    private final Queue<Envelope> queue = new ConcurrentLinkedQueue<Envelope>();

    // these must be implemented; queue used as example
    public void enqueue(ActorRef receiver, Envelope handle) {

    public Envelope dequeue() {
      return queue.poll();

    public int numberOfMessages() {
      return queue.size();

    public boolean hasMessages() {
      return !queue.isEmpty();

    public void cleanUp(ActorRef owner, MessageQueue deadLetters) {
      while (!queue.isEmpty()) {
        deadLetters.enqueue(owner, dequeue());

  // This constructor signature must exist, it will be called by Akka
  public MyUnboundedMailbox(ActorSystem.Settings settings, Config config) {
    // put your initialization code here

  // The create method is called to create the MessageQueue
  public MessageQueue create(Option<ActorRef> owner, Option<ActorSystem> system) {
    return new MyMessageQueue();

And then you specify the FQCN of your MailboxType as the value of the “mailbox-type” in the dispatcher configuration, or the mailbox configuration.


Make sure to include a constructor which takes and com.typesafe.config.Config arguments, as this constructor is invoked reflectively to construct your mailbox type. The config passed in as second argument is that section from the configuration which describes the dispatcher or mailbox setting using this mailbox type; the mailbox type will be instantiated once for each dispatcher or mailbox setting using it.

Found an error in this documentation? The source code for this page can be found here. Please feel free to edit and contribute a pull request.