在docker實例上使用帶有動脈的Akka遠程處理時出錯

Question

首先，對不起我的英語。 Google翻譯對我有很大幫助，哈哈。

我的問題是這樣的：

我有兩個使用akka和java開發的示例項目：example-remote-client.jar和example-remote-server.jar

我正在使用動脈序列化，並且正在嘗試通過akka-remoting將消息從客戶端發送到服務器。

做到這一點的客戶參與者是：

public class ClientActor extends AbstractActor {

    public static Props props() {
        return Props.create(ClientActor.class);

    }

    public ClientActor() {
        ActorSelection selection = getContext().system().actorSelection("akka://server@localhost:5001/user/server-process");
        selection.tell(new MessageRequest(), getSelf());
    }

    public Receive createReceive() {
        return receiveBuilder().match(MessageResponse.class, msg -> {
            System.out.println(msg.getMessage());
        }).build();
    }
}

我的客戶端配置：

akka {
  loglevel = "DEBUG"

  actor {
    provider = remote
    allow-java-serialization = off


    serializers {
      java = "akka.serialization.JavaSerializer"
      myown = "serializers.ExampleByteBufSerializer"
    }

    serialization-bindings {
      "java.lang.String" = myown
      "protocol.MessageRequest" = myown
      "protocol.MessageResponse" = myown
      "java.lang.Boolean" = myown
    }

  }

  remote {
    artery {
      enabled = on
      canonical.hostname = "192.168.0.250"     # external (logical) hostname
      canonical.port = 5000                   # external (logical) port

      bind.hostname = "localhost" # internal (bind) hostname
      bind.port = 10000              # internal (bind) port
    }
  }
}

服務器角色非常虛構，我認為沒有必要在此處粘貼它。 但是它的配置是：

akka {
  loglevel = "DEBUG"

  actor {
    provider = remote
    allow-java-serialization = off


    serializers {
      java = "akka.serialization.JavaSerializer"
      myown = "serializers.ExampleByteBufSerializer"
    }

    serialization-bindings {
      "java.lang.String" = myown
      "protocol.MessageRequest" = myown
      "protocol.MessageResponse" = myown
      "java.lang.Boolean" = myown
    }

  }

  remote {
    artery {
      enabled = on
      canonical.hostname = "192.168.0.250"     # external (logical) hostname
      canonical.port = 5001                   # external (logical) port

      bind.hostname = "localhost" # internal (bind) hostname
      bind.port = 10001              # internal (bind) port
    }
  }
}

兩個jar都部署在運行在同一“ 192.168.0.250計算機”上的docker實例上，如下所示：

CONTAINER ID        IMAGE                      COMMAND                  CREATED             STATUS              PORTS                                            NAMES
d2970bd20371        openjdk:alpine             "sh"                     34 minutes ago      Up 34 minutes       0.0.0.0:5001->10001/tcp                          ex-remoting-server
36a67fea8590        openjdk:alpine             "sh"                     34 minutes ago      Up 34 minutes       0.0.0.0:5000->10000/tcp                          ex-remoting-client

服務器啟動正常，並顯示以下日志：

[DEBUG] [07/04/2017 13:46:18.473] [main] [EventStream(akka://server)] logger log1-Logging$DefaultLogger started
[DEBUG] [07/04/2017 13:46:18.473] [main] [EventStream(akka://server)] Default Loggers started
[DEBUG] [07/04/2017 13:46:18.495] [main] [akka.serialization.Serialization(akka://server)] Replacing JavaSerializer with DisabledJavaSerializer, due to `akka.actor.allow-java-serialization = off`.
[INFO] [07/04/2017 13:46:18.628] [main] [akka.remote.artery.ArteryTransport(akka://server)] Started embedded media driver in directory [/dev/shm/aeron-root-server-efd42dec-452d-406c-8d1d-807e0d8ff7fc]
[INFO] [07/04/2017 13:46:18.693] [main] [akka.remote.artery.ArteryTransport(akka://server)] Remoting started; listening on address: [akka://server@192.168.0.250:5001] with UID [-2663186266051514585]

但是，當我嘗試啟動客戶端時，出現以下錯誤：

[ERROR] [07/04/2017 14:09:05.250] [client-akka.actor.default-dispatcher-10] [akka://server@192.168.0.250:5001/] swallowing exception during message send
io.aeron.exceptions.RegistrationException: Insufficient usable storage for new log of length=50332096 in /dev/shm (shm)
    at io.aeron.ClientConductor.onError(ClientConductor.java:285)
    at io.aeron.DriverListenerAdapter.onMessage(DriverListenerAdapter.java:79)
    at org.agrona.concurrent.broadcast.CopyBroadcastReceiver.receive(CopyBroadcastReceiver.java:100)
    at io.aeron.DriverListenerAdapter.pollMessage(DriverListenerAdapter.java:59)
    at io.aeron.ClientConductor.doWork(ClientConductor.java:422)
    at io.aeron.ClientConductor.awaitResponse(ClientConductor.java:447)
    at io.aeron.ClientConductor.addPublication(ClientConductor.java:177)
    at io.aeron.Aeron.addPublication(Aeron.java:165)
    at akka.remote.artery.AeronSink$$anon$1.<init>(AeronSink.scala:103)
    at akka.remote.artery.AeronSink.createLogicAndMaterializedValue(AeronSink.scala:100)
    at akka.stream.impl.GraphStageIsland.materializeAtomic(PhasedFusingActorMaterializer.scala:627)
    at akka.stream.impl.PhasedFusingActorMaterializer.materialize(PhasedFusingActorMaterializer.scala:458)
    at akka.stream.impl.PhasedFusingActorMaterializer.materialize(PhasedFusingActorMaterializer.scala:420)
    at akka.stream.impl.PhasedFusingActorMaterializer.materialize(PhasedFusingActorMaterializer.scala:415)
    at akka.stream.scaladsl.RunnableGraph.run(Flow.scala:439)
    at akka.remote.artery.Association.akka$remote$artery$Association$$runOutboundOrdinaryMessagesStream(Association.scala:570)
    at akka.remote.artery.Association.runOutboundStreams(Association.scala:510)
    at akka.remote.artery.Association.associate(Association.scala:502)
    at akka.remote.artery.AssociationRegistry.association(Association.scala:763)
    at akka.remote.artery.ArteryTransport.association(ArteryTransport.scala:932)
    at akka.remote.artery.ArteryTransport.send(ArteryTransport.scala:918)
    at akka.remote.RemoteActorRef.$bang(RemoteActorRefProvider.scala:563)
    at akka.actor.ActorRef.tell(ActorRef.scala:124)
    at akka.actor.ActorSelection$.rec$1(ActorSelection.scala:250)
    at akka.actor.ActorSelection$.deliverSelection(ActorSelection.scala:254)
    at akka.actor.ActorSelection.tell(ActorSelection.scala:45)
    at actors.ClientActor.<init>(ClientActor.java:21)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at java.lang.Class.newInstance(Class.java:442)
    at akka.util.Reflect$.instantiate(Reflect.scala:44)
    at akka.actor.NoArgsReflectConstructor.produce(IndirectActorProducer.scala:105)
    at akka.actor.Props.newActor(Props.scala:213)
    at akka.actor.ActorCell.newActor(ActorCell.scala:563)
    at akka.actor.ActorCell.create(ActorCell.scala:589)
    at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:462)
    at akka.actor.ActorCell.systemInvoke(ActorCell.scala:484)
    at akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:282)
    at akka.dispatch.Mailbox.run(Mailbox.scala:223)
    at akka.dispatch.Mailbox.exec(Mailbox.scala:234)
    at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
    at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
    at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
    at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

我也嘗試使用以下“ ActorSelection路徑”發送消息：

“ akka：//服務器@ 192.168.0.250：5001 /用戶/服務器進程”“ akka：//服務器@localhost：5001 /用戶/服務器進程”“ akka：//服務器@ 192.168.0.250：10001 /用戶/ server-process“” akka：// server @ localhost：10001 / user / server-process“

但是錯誤仍然出現。

同樣重要的是，還要澄清服務器參與者的參與者路徑是：

akka：//服務器/用戶/服務器進程

什么東西少了？ 我正在使用akka 2.5.3版本...

謝謝。

Answer 1

我不太確定Akka規范與綁定尋址的工作方式。 但是我的猜測是bind.hostname是實際IP或將通過其偵聽的主機名解析的IP。 在這種情況下， localhost轉換為127.0.0.1 ，這意味着容器將僅接受127.0.0.1連接。

嘗試將bind.hostname設置為0.0.0.0 。 這將允許來自容器外部IP地址的連接（從主機通過端口5001）。

Answer 2

嘗試將/dev/shm卷的大小設置為更大。 在shm_size: 500M -compose文件中，您可以簡單地添加以下選項： shm_size: 500M 。 該卷是aeron用來緩沖消息的共享內存空間。