Akka Sample Projects
Home Page: http://akka.io
This repository contains a number of projects that illustrate various usages of Akka. Samples are written in Scala and Java and use sbt or maven for build definitions.
The Akka family of projects is managed by teams at Lightbend with help from the community.
Akka is licensed under the Business Source License 1.1, please see the Akka License FAQ.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
I will do it after PR akka/akka#22472
[JVM-1] [ERROR] [05/24/2017 15:16:17.296] [VotingServiceSpec-akka.remote.default-remote-dispatcher-13] [akka.tcp://VotingServiceSpec@localhost:61200/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FVotingServiceSpec%40localhost%3A61198-0/endpointWriter] Transient association error (association remains live)
[JVM-1] akka.remote.OversizedPayloadException: Discarding oversized payload sent to Actor[akka.tcp://VotingServiceSpec@localhost:61198/]: max allowed size 128000 bytes, actual size of encoded class akka.actor.ActorSelectionMessage was 139144 bytes
also with Akka 2.5.2
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running sample.cluster.client.grpc.ClusterClientTest
[INFO] [11/25/2019 12:54:47.333] [main] [akka.remote.artery.tcp.ArteryTcpTransport(akka://ClusterClientTest)] Remoting started with transport [Artery tcp]; listening on address [akka://[email protected]:39803] with UID [-5395267153817664087]
[INFO] [11/25/2019 12:54:47.368] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Starting up, Akka version [2.6.0-M8] ...
[INFO] [11/25/2019 12:54:47.477] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Registered cluster JMX MBean [akka:type=Cluster]
[INFO] [11/25/2019 12:54:47.477] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Started up successfully
[INFO] [11/25/2019 12:54:47.581] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - No seed-nodes configured, manual cluster join required, see https://doc.akka.io/docs/akka/current/cluster-usage.html#joining-to-seed-nodes
[INFO] [11/25/2019 12:54:47.695] [main] [akka.remote.artery.tcp.ArteryTcpTransport(akka://ClusterClientTest)] Remoting started with transport [Artery tcp]; listening on address [akka://[email protected]:39749] with UID [4842462293398171948]
[INFO] [11/25/2019 12:54:47.699] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - Starting up, Akka version [2.6.0-M8] ...
[WARN] [11/25/2019 12:54:47.709] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Could not register Cluster JMX MBean with name=akka:type=Cluster as it is already registered. If you are running multiple clusters in the same JVM, set 'akka.cluster.jmx.multi-mbeans-in-same-jvm = on' in config
[INFO] [11/25/2019 12:54:47.710] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - Started up successfully
[INFO] [11/25/2019 12:54:47.716] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - No seed-nodes configured, manual cluster join required, see https://doc.akka.io/docs/akka/current/cluster-usage.html#joining-to-seed-nodes
[INFO] [11/25/2019 12:54:47.808] [main] [akka.remote.artery.tcp.ArteryTcpTransport(akka://ClusterClientTest)] Remoting started with transport [Artery tcp]; listening on address [akka://[email protected]:42605] with UID [3761732213052592203]
[INFO] [11/25/2019 12:54:47.811] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - Starting up, Akka version [2.6.0-M8] ...
[WARN] [11/25/2019 12:54:47.817] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Could not register Cluster JMX MBean with name=akka:type=Cluster as it is already registered. If you are running multiple clusters in the same JVM, set 'akka.cluster.jmx.multi-mbeans-in-same-jvm = on' in config
[INFO] [11/25/2019 12:54:47.817] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - Started up successfully
[INFO] [11/25/2019 12:54:47.822] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - No seed-nodes configured, manual cluster join required, see https://doc.akka.io/docs/akka/current/cluster-usage.html#joining-to-seed-nodes
[INFO] [11/25/2019 12:54:47.917] [main] [akka.remote.artery.tcp.ArteryTcpTransport(akka://ClusterClientTest)] Remoting started with transport [Artery tcp]; listening on address [akka://[email protected]:37273] with UID [1981176973620231368]
[INFO] [11/25/2019 12:54:47.924] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Starting up, Akka version [2.6.0-M8] ...
[WARN] [11/25/2019 12:54:47.936] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Could not register Cluster JMX MBean with name=akka:type=Cluster as it is already registered. If you are running multiple clusters in the same JVM, set 'akka.cluster.jmx.multi-mbeans-in-same-jvm = on' in config
[INFO] [11/25/2019 12:54:47.937] [main] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Started up successfully
[INFO] [11/25/2019 12:54:47.943] [ClusterClientTest-akka.actor.internal-dispatcher-4] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - No seed-nodes configured, manual cluster join required, see https://doc.akka.io/docs/akka/current/cluster-usage.html#joining-to-seed-nodes
[INFO] [11/25/2019 12:54:48.051] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Node [akka://[email protected]:39803] is JOINING itself (with roles [dc-default]) and forming new cluster
[INFO] [11/25/2019 12:54:48.059] [main] [ClusterClientReceptionist] Starting ClusterClientReceptionist gRPC server at 127.0.0.1:50051
[INFO] [11/25/2019 12:54:48.149] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - is the new leader among reachable nodes (more leaders may exist)
[INFO] [11/25/2019 12:54:48.177] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Leader is moving node [akka://[email protected]:39803] to [Up]
[INFO] [11/25/2019 12:54:48.926] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Node [akka://[email protected]:42605] is JOINING, roles [dc-default]
[INFO] [11/25/2019 12:54:48.935] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Node [akka://[email protected]:37273] is JOINING, roles [dc-default]
[INFO] [11/25/2019 12:54:49.020] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Node [akka://[email protected]:39749] is JOINING, roles [dc-default]
[INFO] [11/25/2019 12:54:49.029] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Welcome from [akka://[email protected]:39803]
[INFO] [11/25/2019 12:54:49.036] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - Welcome from [akka://[email protected]:39803]
[INFO] [11/25/2019 12:54:49.048] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - Welcome from [akka://[email protected]:39803]
[INFO] [11/25/2019 12:54:49.615] [main] [ClusterClientReceptionist] Starting ClusterClientReceptionist gRPC server at 127.0.0.1:50052
[INFO] [11/25/2019 12:54:49.625] [Thread-9] [ClusterClientReceptionist] ClusterClientReceptionist gRPC server stopped successfully
[INFO] [11/25/2019 12:54:49.628] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Leader is moving node [akka://[email protected]:37273] to [Up]
[INFO] [11/25/2019 12:54:49.628] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Leader is moving node [akka://[email protected]:39749] to [Up]
[INFO] [11/25/2019 12:54:49.628] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Leader is moving node [akka://[email protected]:42605] to [Up]
[INFO] [11/25/2019 12:54:49.660] [main] [ClusterClientReceptionist] Starting ClusterClientReceptionist gRPC server at 127.0.0.1:50053
[INFO] [11/25/2019 12:54:49.664] [Thread-10] [ClusterClientReceptionist] ClusterClientReceptionist gRPC server stopped successfully
[INFO] [11/25/2019 12:54:49.684] [main] [ClusterClientReceptionist] Starting ClusterClientReceptionist gRPC server at 127.0.0.1:50054
[INFO] [11/25/2019 12:54:49.697] [Thread-11] [ClusterClientReceptionist] ClusterClientReceptionist gRPC server stopped successfully
[INFO] [11/25/2019 12:54:49.734] [Thread-12] [ClusterClientReceptionist] ClusterClientReceptionist gRPC server stopped successfully
[INFO] [11/25/2019 12:54:50.629] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - is no longer leader
[INFO] [11/25/2019 12:54:50.998] [ClusterClientTest-akka.actor.internal-dispatcher-4] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - is the new leader among reachable nodes (more leaders may exist)
[INFO] [11/25/2019 12:54:52.779] [ClusterClientTest-akka.actor.default-dispatcher-6] [akka://ClusterClientTest/user/client1] New session for Actor[akka://ClusterClientTest/system/testProbe-1#-1772270167]
[INFO] [11/25/2019 12:54:53.926] [ClusterClientTest-akka.actor.default-dispatcher-8] [ClusterClientReceptionist] New session [0a151923-45a7-4163-a49b-631f75a85ed0]
[INFO] [11/25/2019 12:54:54.242] [ClusterClientTest-akka.actor.default-dispatcher-9] [akka://ClusterClientTest/user/ask-sesion-client] New session for Actor[akka://ClusterClientTest/temp/$a]
[INFO] [11/25/2019 12:54:54.278] [ClusterClientTest-akka.actor.default-dispatcher-8] [ClusterClientReceptionist] New session [30fc2d3b-a763-4785-849a-63267c255fcc]
[INFO] [11/25/2019 12:54:54.279] [Thread-13] [ClusterClientReceptionist] Session [0a151923-45a7-4163-a49b-631f75a85ed0] completed successfully: Done
[INFO] [11/25/2019 12:54:54.305] [ClusterClientTest-akka.actor.default-dispatcher-9] [akka://ClusterClientTest/user/ask-sesion-client] New session for Actor[akka://ClusterClientTest/temp/$b]
[INFO] [11/25/2019 12:54:54.319] [Thread-14] [akka://ClusterClientTest/user/ask-sesion-client] Session completed successfully for Actor[akka://ClusterClientTest/temp/$a]: Done
[INFO] [11/25/2019 12:54:54.338] [ClusterClientTest-akka.actor.default-dispatcher-8] [ClusterClientReceptionist] New session [0d8de4b7-8743-41e5-9e9e-1e8d064bccda]
[INFO] [11/25/2019 12:54:54.341] [Thread-15] [ClusterClientReceptionist] Session [30fc2d3b-a763-4785-849a-63267c255fcc] completed with failure: akka.http.scaladsl.model.http2.PeerClosedStreamException: Stream with ID [3] was closed by peer with code CANCEL(0x08)
[INFO] [11/25/2019 12:54:54.371] [Thread-16] [akka://ClusterClientTest/user/ask-sesion-client] Session completed successfully for Actor[akka://ClusterClientTest/temp/$b]: Done
[INFO] [11/25/2019 12:54:54.375] [Thread-17] [ClusterClientReceptionist] Session [0d8de4b7-8743-41e5-9e9e-1e8d064bccda] completed with failure: akka.http.scaladsl.model.http2.PeerClosedStreamException: Stream with ID [5] was closed by peer with code CANCEL(0x08)
[INFO] [11/25/2019 12:54:55.795] [ClusterClientTest-akka.actor.default-dispatcher-11] [akka://ClusterClientTest/user/client] New session for Actor[akka://ClusterClientTest/system/testProbe-1#-1772270167]
[INFO] [11/25/2019 12:54:55.818] [ClusterClientTest-akka.actor.default-dispatcher-8] [ClusterClientReceptionist] New session [b699b262-c662-4ac4-9b62-4a4e1f37b3a0]
[INFO] [11/25/2019 12:54:55.841] [Thread-24] [ClusterClientReceptionist] Session [b699b262-c662-4ac4-9b62-4a4e1f37b3a0] completed successfully: Done
[INFO] [11/25/2019 12:54:55.930] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Marked address [akka://[email protected]:39803] as [Leaving]
[INFO] [11/25/2019 12:54:57.138] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Leader is moving node [akka://[email protected]:39803] to [Exiting]
[INFO] [11/25/2019 12:54:57.147] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Exiting completed
[INFO] [11/25/2019 12:54:57.151] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Shutting down...
[INFO] [11/25/2019 12:54:57.151] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39803] - Successfully shut down
[INFO] [11/25/2019 12:54:57.163] [ClusterClientTest-akka.actor.internal-dispatcher-4] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Exiting confirmed [akka://[email protected]:39803]
[INFO] [11/25/2019 12:54:57.169] [ClusterClientTest-akka.actor.default-dispatcher-28] [akka://ClusterClientTest/system/cluster/core/daemon] Message [akka.cluster.GossipEnvelope] from Actor[akka://[email protected]:42605/system/cluster/core/daemon#2081416629] to Actor[akka://ClusterClientTest/system/cluster/core/daemon#1621349979] was not delivered. [1] dead letters encountered. If this is not an expected behavior then Actor[akka://ClusterClientTest/system/cluster/core/daemon#1621349979] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[INFO] [11/25/2019 12:54:57.171] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka://[email protected]:39803/system/remoting-terminator] Shutting down remote daemon.
[INFO] [11/25/2019 12:54:57.174] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka://[email protected]:39803/system/remoting-terminator] Remote daemon shut down; proceeding with flushing remote transports.
[INFO] [11/25/2019 12:54:57.174] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - Exiting confirmed [akka://[email protected]:39803]
[WARN] [11/25/2019 12:54:57.213] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-2)] [outbound connection to [akka://[email protected]:42605], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:54:57.216] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-2)] [outbound connection to [akka://[email protected]:39749], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:54:57.219] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-2)] [outbound connection to [akka://[email protected]:39749], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:54:57.221] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-2)] [outbound connection to [akka://[email protected]:37273], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:54:57.222] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-2)] [outbound connection to [akka://[email protected]:37273], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:54:57.224] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-2)] [outbound connection to [akka://[email protected]:42605], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[INFO] [11/25/2019 12:54:57.249] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka://[email protected]:39803/system/remoting-terminator] Remoting shut down.
[INFO] [11/25/2019 12:54:57.282] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - Marked address [akka://[email protected]:39749] as [Leaving]
[INFO] [11/25/2019 12:54:58.202] [ClusterClientTest-akka.remote.default-remote-dispatcher-12] [akka.remote.artery.Association(akka://ClusterClientTest)] Association to [akka://[email protected]:39803] having UID [-5395267153817664087] has been stopped. All messages to this UID will be delivered to dead letters. Reason: ActorSystem terminated
[INFO] [11/25/2019 12:54:58.207] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka.remote.artery.Association(akka://ClusterClientTest)] Association to [akka://[email protected]:39803] having UID [-5395267153817664087] has been stopped. All messages to this UID will be delivered to dead letters. Reason: ActorSystem terminated
[INFO] [11/25/2019 12:54:58.207] [ClusterClientTest-akka.remote.default-remote-dispatcher-13] [akka.remote.artery.Association(akka://ClusterClientTest)] Association to [akka://[email protected]:39803] having UID [-5395267153817664087] has been stopped. All messages to this UID will be delivered to dead letters. Reason: ActorSystem terminated
[INFO] [11/25/2019 12:54:59.189] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Leader is moving node [akka://[email protected]:39749] to [Exiting]
[INFO] [11/25/2019 12:54:59.190] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Leader is removing confirmed Exiting node [akka://[email protected]:39803]
[INFO] [11/25/2019 12:54:59.219] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - Exiting completed
[INFO] [11/25/2019 12:54:59.226] [ClusterClientTest-akka.actor.internal-dispatcher-4] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Exiting confirmed [akka://[email protected]:39749]
[INFO] [11/25/2019 12:54:59.240] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - Shutting down...
[INFO] [11/25/2019 12:54:59.242] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - Exiting confirmed [akka://[email protected]:39749]
[WARN] [11/25/2019 12:54:59.246] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Could not unregister Cluster JMX MBean with name=akka:type=Cluster as it was not found. If you are running multiple clusters in the same JVM, set 'akka.cluster.jmx.multi-mbeans-in-same-jvm = on' in config
[INFO] [11/25/2019 12:54:59.250] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:39749] - Successfully shut down
[INFO] [11/25/2019 12:54:59.252] [ClusterClientTest-akka.actor.default-dispatcher-10] [akka://ClusterClientTest/system/cluster/core/daemon] Message [akka.cluster.GossipEnvelope] from Actor[akka://[email protected]:37273/system/cluster/core/daemon#1628629284] to Actor[akka://ClusterClientTest/system/cluster/core/daemon#509197998] was not delivered. [1] dead letters encountered. If this is not an expected behavior then Actor[akka://ClusterClientTest/system/cluster/core/daemon#509197998] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[INFO] [11/25/2019 12:54:59.255] [ClusterClientTest-akka.actor.default-dispatcher-8] [akka://ClusterClientTest/system/cluster/core/daemon] Message [akka.cluster.GossipEnvelope] from Actor[akka://[email protected]:37273/system/cluster/core/daemon#1628629284] to Actor[akka://ClusterClientTest/system/cluster/core/daemon#509197998] was not delivered. [2] dead letters encountered. If this is not an expected behavior then Actor[akka://ClusterClientTest/system/cluster/core/daemon#509197998] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[INFO] [11/25/2019 12:54:59.259] [ClusterClientTest-akka.actor.default-dispatcher-8] [akka://ClusterClientTest/system/cluster/core/daemon] Message [akka.cluster.GossipEnvelope] from Actor[akka://[email protected]:42605/system/cluster/core/daemon#2081416629] to Actor[akka://ClusterClientTest/system/cluster/core/daemon#509197998] was not delivered. [3] dead letters encountered. If this is not an expected behavior then Actor[akka://ClusterClientTest/system/cluster/core/daemon#509197998] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[INFO] [11/25/2019 12:54:59.260] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka://[email protected]:39749/system/remoting-terminator] Shutting down remote daemon.
[INFO] [11/25/2019 12:54:59.261] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka://[email protected]:39749/system/remoting-terminator] Remote daemon shut down; proceeding with flushing remote transports.
[INFO] [11/25/2019 12:55:00.208] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Leader is removing confirmed Exiting node [akka://[email protected]:39749]
[INFO] [11/25/2019 12:55:00.277] [ClusterClientTest-akka.remote.default-remote-dispatcher-13] [akka.remote.artery.Association(akka://ClusterClientTest)] Association to [akka://[email protected]:39749] having UID [4842462293398171948] has been stopped. All messages to this UID will be delivered to dead letters. Reason: ActorSystem terminated
[WARN] [11/25/2019 12:55:00.283] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-5)] [outbound connection to [akka://[email protected]:37273], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:55:00.284] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-5)] [outbound connection to [akka://[email protected]:37273], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:55:00.284] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-5)] [outbound connection to [akka://[email protected]:42605], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:55:00.284] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-5)] [outbound connection to [akka://[email protected]:42605], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[INFO] [11/25/2019 12:55:00.285] [ClusterClientTest-akka.remote.default-remote-dispatcher-12] [akka.remote.artery.Association(akka://ClusterClientTest)] Association to [akka://[email protected]:39749] having UID [4842462293398171948] has been stopped. All messages to this UID will be delivered to dead letters. Reason: ActorSystem terminated
[INFO] [11/25/2019 12:55:00.293] [ClusterClientTest-akka.remote.default-remote-dispatcher-11] [akka://[email protected]:39749/system/remoting-terminator] Remoting shut down.
[INFO] [11/25/2019 12:55:00.315] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - Marked address [akka://[email protected]:42605] as [Leaving]
[INFO] [11/25/2019 12:55:01.230] [ClusterClientTest-akka.actor.internal-dispatcher-4] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Leader is moving node [akka://[email protected]:42605] to [Exiting]
[INFO] [11/25/2019 12:55:01.236] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - Exiting completed
[INFO] [11/25/2019 12:55:01.237] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - Shutting down...
[WARN] [11/25/2019 12:55:01.238] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Could not unregister Cluster JMX MBean with name=akka:type=Cluster as it was not found. If you are running multiple clusters in the same JVM, set 'akka.cluster.jmx.multi-mbeans-in-same-jvm = on' in config
[INFO] [11/25/2019 12:55:01.238] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:42605] - Successfully shut down
[INFO] [11/25/2019 12:55:01.251] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Exiting confirmed [akka://[email protected]:42605]
[INFO] [11/25/2019 12:55:01.252] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka://[email protected]:42605/system/remoting-terminator] Shutting down remote daemon.
[INFO] [11/25/2019 12:55:01.252] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka://[email protected]:42605/system/remoting-terminator] Remote daemon shut down; proceeding with flushing remote transports.
[ERROR] [11/25/2019 12:55:02.066] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka.remote.artery.Association(akka://ClusterClientTest)] Outbound message stream to [akka://[email protected]:39803] failed after shutdown. (akka.remote.artery.Association$OutboundStreamStopQuarantinedSignal$: )
[ERROR] [11/25/2019 12:55:02.066] [ClusterClientTest-akka.remote.default-remote-dispatcher-12] [akka.remote.artery.Association(akka://ClusterClientTest)] Outbound control stream to [akka://[email protected]:39803] failed after shutdown. (akka.remote.artery.Association$OutboundStreamStopQuarantinedSignal$: )
[INFO] [11/25/2019 12:55:02.207] [ClusterClientTest-akka.actor.default-dispatcher-9] [akka://ClusterClientTest/deadLetters] Message [akka.remote.artery.SystemMessageDelivery$ClearSystemMessageDelivery] to Actor[akka://ClusterClientTest/deadLetters] was not delivered. [1] dead letters encountered. If this is not an expected behavior then Actor[akka://ClusterClientTest/deadLetters] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[INFO] [11/25/2019 12:55:02.249] [ClusterClientTest-akka.actor.internal-dispatcher-5] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Leader is removing confirmed Exiting node [akka://[email protected]:42605]
[INFO] [11/25/2019 12:55:02.267] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka.remote.artery.Association(akka://ClusterClientTest)] Association to [akka://[email protected]:42605] having UID [3761732213052592203] has been stopped. All messages to this UID will be delivered to dead letters. Reason: ActorSystem terminated
[WARN] [11/25/2019 12:55:02.276] [ClusterClientTest-akka.remote.default-remote-dispatcher-12] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-8)] [outbound connection to [akka://[email protected]:37273], control stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[WARN] [11/25/2019 12:55:02.276] [ClusterClientTest-akka.remote.default-remote-dispatcher-7] [akka.stream.Log(akka://ClusterClientTest/system/Materializers/StreamSupervisor-8)] [outbound connection to [akka://[email protected]:37273], message stream] Upstream failed, cause: StreamTcpException: The connection has been aborted
[INFO] [11/25/2019 12:55:02.280] [ClusterClientTest-akka.remote.default-remote-dispatcher-12] [akka://[email protected]:42605/system/remoting-terminator] Remoting shut down.
[INFO] [11/25/2019 12:55:02.298] [ClusterClientTest-akka.actor.internal-dispatcher-3] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Marked address [akka://[email protected]:37273] as [Leaving]
[INFO] [11/25/2019 12:55:03.267] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Leader is moving node [akka://[email protected]:37273] to [Exiting]
[INFO] [11/25/2019 12:55:03.272] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Exiting completed
[INFO] [11/25/2019 12:55:03.273] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Shutting down...
[WARN] [11/25/2019 12:55:03.274] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Could not unregister Cluster JMX MBean with name=akka:type=Cluster as it was not found. If you are running multiple clusters in the same JVM, set 'akka.cluster.jmx.multi-mbeans-in-same-jvm = on' in config
[INFO] [11/25/2019 12:55:03.275] [ClusterClientTest-akka.actor.internal-dispatcher-2] [akka.cluster.Cluster(akka://ClusterClientTest)] Cluster Node [akka://[email protected]:37273] - Successfully shut down
[INFO] [11/25/2019 12:55:03.281] [ClusterClientTest-akka.remote.default-remote-dispatcher-13] [akka://[email protected]:37273/system/remoting-terminator] Shutting down remote daemon.
[INFO] [11/25/2019 12:55:03.282] [ClusterClientTest-akka.remote.default-remote-dispatcher-13] [akka://[email protected]:37273/system/remoting-terminator] Remote daemon shut down; proceeding with flushing remote transports.
[INFO] [11/25/2019 12:55:03.289] [ClusterClientTest-akka.remote.default-remote-dispatcher-13] [akka://[email protected]:37273/system/remoting-terminator] Remoting shut down.
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 18.486 sec <<< FAILURE!
step1_shouldJoinNodesToCluster(sample.cluster.client.grpc.ClusterClientTest) Time elapsed: 4.673 sec <<< FAILURE!
java.lang.AssertionError: assertion failed: expected 1, found 0
at scala.Predef$.assert(Predef.scala:223)
at akka.testkit.TestKitBase.expectMsg_internal(TestKit.scala:419)
at akka.testkit.TestKitBase.expectMsg(TestKit.scala:395)
at akka.testkit.TestKitBase.expectMsg$(TestKit.scala:395)
at akka.testkit.TestKit.expectMsg(TestKit.scala:928)
at akka.testkit.javadsl.TestKit.expectMsg(TestKit.scala:464)
at sample.cluster.client.grpc.ClusterClientTest.lambda$awaitCount$0(ClusterClientTest.java:147)
at akka.testkit.javadsl.TestKit.$anonfun$awaitAssert$1(TestKit.scala:379)
at akka.testkit.TestKitBase.poll$2(TestKit.scala:327)
at akka.testkit.TestKitBase.awaitAssert(TestKit.scala:344)
at akka.testkit.TestKitBase.awaitAssert$(TestKit.scala:316)
at akka.testkit.TestKit.awaitAssert(TestKit.scala:928)
at akka.testkit.javadsl.TestKit.awaitAssert(TestKit.scala:379)
at sample.cluster.client.grpc.ClusterClientTest.awaitCount(ClusterClientTest.java:144)
at sample.cluster.client.grpc.ClusterClientTest.step1_shouldJoinNodesToCluster(ClusterClientTest.java:170)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Results :
Failed tests: step1_shouldJoinNodesToCluster(sample.cluster.client.grpc.ClusterClientTest): assertion failed: expected 1, found 0
This relates to syncing this repo for #25746
E.g.:
implicit val cluster: akka.cluster.Cluster
class VotingService extends Actor {
val replicator = DistributedData(context.system).replicator
implicit val cluster = Cluster(context.system)
}class VotingService extends Actor {
val replicator = DistributedData(context.system).replicator
implicit val node = DistributedData(context.system).selfUniqueAddress
}from "com.typesafe.akka.samples"
we can do this as a global search replace across all samples in 2.6 branch
from typesafehub (activator templates):
https://github.com/typesafehub/activator-akka-distributed-workers
https://github.com/typesafehub/activator-akka-distributed-workers-java
Travis build failure.
[info] * sample.distributeddata.ReplicatedMetricsSpec
[JVM-1] Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
[JVM-2] Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
[JVM-3] Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
[JVM-1] [INFO] [01/10/2018 16:19:42.996] [ScalaTest-main] [akka.remote.Remoting] Starting remoting
[JVM-3] [INFO] [01/10/2018 16:19:43.088] [ScalaTest-main] [akka.remote.Remoting] Starting remoting
[JVM-2] [INFO] [01/10/2018 16:19:43.290] [ScalaTest-main] [akka.remote.Remoting] Starting remoting
[JVM-1] [INFO] [01/10/2018 16:19:43.475] [ScalaTest-main] [akka.remote.Remoting] Remoting started; listening on addresses :[akka.tcp://ReplicatedMetricsSpec@localhost:37751]
[JVM-1] [INFO] [01/10/2018 16:19:43.479] [ScalaTest-main] [akka.remote.Remoting] Remoting now listens on addresses: [akka.tcp://ReplicatedMetricsSpec@localhost:37751]
[JVM-1] [INFO] [01/10/2018 16:19:43.534] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Starting up...
[JVM-3] [INFO] [01/10/2018 16:19:43.735] [ScalaTest-main] [akka.remote.Remoting] Remoting started; listening on addresses :[akka.tcp://ReplicatedMetricsSpec@localhost:39789]
[JVM-3] [INFO] [01/10/2018 16:19:43.738] [ScalaTest-main] [akka.remote.Remoting] Remoting now listens on addresses: [akka.tcp://ReplicatedMetricsSpec@localhost:39789]
[JVM-3] [INFO] [01/10/2018 16:19:43.800] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:39789] - Starting up...
[JVM-1] [INFO] [01/10/2018 16:19:43.825] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Registered cluster JMX MBean [akka:type=Cluster]
[JVM-1] [INFO] [01/10/2018 16:19:43.826] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Started up successfully
[JVM-1] [INFO] [01/10/2018 16:19:43.949] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-6] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - No seed-nodes configured, manual cluster join required
[JVM-2] [INFO] [01/10/2018 16:19:44.041] [ScalaTest-main] [akka.remote.Remoting] Remoting started; listening on addresses :[akka.tcp://ReplicatedMetricsSpec@localhost:46825]
[JVM-2] [INFO] [01/10/2018 16:19:44.043] [ScalaTest-main] [akka.remote.Remoting] Remoting now listens on addresses: [akka.tcp://ReplicatedMetricsSpec@localhost:46825]
[JVM-2] [INFO] [01/10/2018 16:19:44.068] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:46825] - Starting up...
[JVM-3] [INFO] [01/10/2018 16:19:44.296] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:39789] - Registered cluster JMX MBean [akka:type=Cluster]
[JVM-3] [INFO] [01/10/2018 16:19:44.298] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:39789] - Started up successfully
[JVM-2] [INFO] [01/10/2018 16:19:44.398] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:46825] - Registered cluster JMX MBean [akka:type=Cluster]
[JVM-2] [INFO] [01/10/2018 16:19:44.398] [ScalaTest-main] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:46825] - Started up successfully
[JVM-3] [INFO] [01/10/2018 16:19:44.443] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-4] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:39789] - No seed-nodes configured, manual cluster join required
[JVM-2] [INFO] [01/10/2018 16:19:44.542] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-2] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:46825] - No seed-nodes configured, manual cluster join required
[JVM-1] [INFO] [01/10/2018 16:19:44.818] [ScalaTest-main] [ReplicatedMetricsSpecMultiJvmNode1(akka://ReplicatedMetricsSpec)] Role [node-1] started with address [akka.tcp://ReplicatedMetricsSpec@localhost:37751]
[JVM-2] [INFO] [01/10/2018 16:19:45.071] [ScalaTest-main] [ReplicatedMetricsSpecMultiJvmNode2(akka://ReplicatedMetricsSpec)] Role [node-2] started with address [akka.tcp://ReplicatedMetricsSpec@localhost:46825]
[JVM-3] [INFO] [01/10/2018 16:19:45.102] [ScalaTest-main] [ReplicatedMetricsSpecMultiJvmNode3(akka://ReplicatedMetricsSpec)] Role [node-3] started with address [akka.tcp://ReplicatedMetricsSpec@localhost:39789]
[JVM-1] Run starting. Expected test count is: 3
[JVM-1] ReplicatedMetricsSpecMultiJvmNode1:
[JVM-1] Demo of a replicated metrics
[JVM-2] Run starting. Expected test count is: 3
[JVM-1] [INFO] [01/10/2018 16:19:45.486] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-5] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] is JOINING, roles [dc-default]
[JVM-1] [INFO] [01/10/2018 16:19:45.520] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-5] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Leader is moving node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] to [Up]
[JVM-2] ReplicatedMetricsSpecMultiJvmNode2:
[JVM-3] Run starting. Expected test count is: 3
[JVM-3] ReplicatedMetricsSpecMultiJvmNode3:
[JVM-2] Demo of a replicated metrics
[JVM-3] Demo of a replicated metrics
[JVM-1] [INFO] [01/10/2018 16:19:46.215] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-4] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Node [akka.tcp://ReplicatedMetricsSpec@localhost:46825] is JOINING, roles [dc-default]
[JVM-1] [INFO] [01/10/2018 16:19:46.221] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-16] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Node [akka.tcp://ReplicatedMetricsSpec@localhost:39789] is JOINING, roles [dc-default]
[JVM-3] [INFO] [01/10/2018 16:19:46.387] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-2] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:39789] - Welcome from [akka.tcp://ReplicatedMetricsSpec@localhost:37751]
[JVM-2] [INFO] [01/10/2018 16:19:46.529] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-6] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:46825] - Welcome from [akka.tcp://ReplicatedMetricsSpec@localhost:37751]
[JVM-2] [INFO] [01/10/2018 16:19:46.753] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-18] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:46825] - Ignoring received gossip from unknown [UniqueAddress(akka.tcp://ReplicatedMetricsSpec@localhost:39789,-1207333420)]
[JVM-1] [INFO] [01/10/2018 16:19:46.936] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-3] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Leader is moving node [akka.tcp://ReplicatedMetricsSpec@localhost:39789] to [Up]
[JVM-1] [INFO] [01/10/2018 16:19:46.936] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-3] [akka.cluster.Cluster(akka://ReplicatedMetricsSpec)] Cluster Node [akka.tcp://ReplicatedMetricsSpec@localhost:37751] - Leader is moving node [akka.tcp://ReplicatedMetricsSpec@localhost:46825] to [Up]
[JVM-3] - must join cluster
[JVM-1] - must join cluster
[JVM-2] - must join cluster
[JVM-3] - must replicate metrics *** FAILED ***
[JVM-3] 2 was not equal to 3 (ReplicatedMetricsSpec.scala:66)
[JVM-1] [ERROR] [01/10/2018 16:19:50.466] [ReplicatedMetricsSpec-akka.actor.default-dispatcher-4] [akka://ReplicatedMetricsSpec/user/controller/barriers] RoleName(node-1) tried to enter 'after-2' while we were waiting for 'after-3' (akka.remote.testconductor.BarrierCoordinator$WrongBarrier: RoleName(node-1) tried to enter 'after-2' while we were waiting for 'after-3')
[JVM-3] - must cleanup removed node *** FAILED ***
[JVM-3] java.lang.RuntimeException: barrier failed: after-3
[JVM-3] at akka.remote.testconductor.ClientFSM$$anonfun$3.applyOrElse(Player.scala:222)
[JVM-3] at akka.remote.testconductor.ClientFSM$$anonfun$3.applyOrElse(Player.scala:197)
[JVM-3] at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:34)
To illustrate how to setup tests.
It's used in https://github.com/akka/akka-samples/tree/2.5/akka-sample-cqrs-scala and that can probably be a good example to point at, but it needs to be updated and should also have a java version.
Hi,
I am working on upgrading the akka distributed workers (in similar lines with the distributed works example), master is ClusterSingletonManager and WorkersSystem is coming up, but getting the strange Association error.
Using Akka 2.4.17 also faced the same issue with akka 2.5.4.
Please suggest, looks like we are stuck here.
2018-03-30 10:31:02,963 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-25) [INFO] [03/30/2018 10:31:02.953] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Remoting started; listening on addresses :[akka.tcp://[email protected]:4002]
2018-03-30 10:31:02,965 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-30) [INFO] [03/30/2018 10:31:02.960] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Remoting now listens on addresses: [akka.tcp://[email protected]:4002]
2018-03-30 10:31:03,046 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-15) [INFO] [03/30/2018 10:31:03.021] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Starting remoting
2018-03-30 10:31:03,083 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-28) [INFO] [03/30/2018 10:31:03.077] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Remoting started; listening on addresses :[akka.tcp://[email protected]:4003]
2018-03-30 10:31:03,100 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-35) [INFO] [03/30/2018 10:31:03.077] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Remoting now listens on addresses: [akka.tcp://[email protected]:4003]
2018-03-30 10:31:03,145 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-14) [INFO] [03/30/2018 10:31:03.144] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Starting remoting
2018-03-30 10:31:03,185 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-27) [INFO] [03/30/2018 10:31:03.183] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Remoting started; listening on addresses :[akka.tcp://[email protected]:4004]
2018-03-30 10:31:03,186 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-29) [INFO] [03/30/2018 10:31:03.184] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Remoting now listens on addresses: [akka.tcp://[email protected]:4004]
2018-03-30 10:31:03,231 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-10) [INFO] [03/30/2018 10:31:03.230] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Starting remoting
2018-03-30 10:31:03,259 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-24) [INFO] [03/30/2018 10:31:03.255] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Remoting started; listening on addresses :[akka.tcp://[email protected]:4005]
2018-03-30 10:31:03,261 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-28) [INFO] [03/30/2018 10:31:03.256] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Remoting now listens on addresses: [akka.tcp://[email protected]:4005]
2018-03-30 10:31:03,325 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-13) [INFO] [03/30/2018 10:31:03.324] [ServerService Thread Pool -- 78] [akka.remote.Remoting] Starting remoting
_**2018-03-30 10:31:03,331 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-5) [ERROR] **[03/30/2018 10:31:03.330] [WorkerSystem-akka.remote.default-remote-dispatcher-22] [akka.tcp://[email protected]:4002/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%40127.0.0.1%3A2551-0/endpointWriter] AssociationError [akka.tcp://[email protected]:4002] -> [akka.tcp://[email protected]:2551]: Error [[B cannot be cast to [C] [
2018-03-30 10:31:03,331 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-5) java.lang.ClassCastException: [B cannot be cast to [C****_
2018-03-30 10:31:03,332 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-5) at deployment.jaxrpc.war//akka.remote.artery.FastHash$.ofString(LruBoundedCache.scala:18)
2018-03-30 10:31:03,332 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-5) at deployment.jaxrpc.war//akka.remote.serialization.ActorRefResolveCache.hash(ActorRefResolveCache.scala:61)
2018-03-30 10:31:03,332 INFO [stdout] (WorkerSystem-akka.actor.default-dispatcher-5) at deployment.jaxrpc.war//akka.remote.serialization.ActorRefResolveCache.hash(ActorRefResolveCache.scala:55)
Hi! I'm facing a weird issue with akka-samples-cluster-java and would like to know, if it's a bug or just me doing something wrong. Thanks in advance!
My configuration is mostly default:
Here are the steps that I'm following:
The problem is that now everybody is stuck.
State of A:
[akka.cluster.Cluster(akka://ClusterSystem)] Cluster Node [akka://[email protected]:2551] - Leader can currently not perform its duties, reachability status: [akka://[email protected]:2551 -> akka://[email protected]:2552: Terminated [Terminated] (3), akka://[email protected]:2551 -> akka://[email protected]:49837: Unreachable [Unreachable] (1), akka://[email protected]:45971 -> akka://[email protected]:2552: Unreachable [Terminated] (1), akka://[email protected]:45971 -> akka://[email protected]:49837: Unreachable [Unreachable] (2)], member status: [akka://[email protected]:2551 Up seen=true, akka://[email protected]:2552 Down seen=false, akka://[email protected]:45971 WeaklyUp seen=true, akka://[email protected]:49837 Up seen=false]
State of B' (keeps printing the same message):
[akka://[email protected]:2552/system/cluster/core/daemon/joinSeedNodeProcess-79] Received InitJoinAck message from [Actor[akka://[email protected]:2551/system/cluster/core/daemon#455455414]] to [akka://[email protected]:2552]
State of C' (keeps printing the same ERROR message):
[akka://[email protected]:45971/system/cluster/core/daemon] Cluster Node [akka://[email protected]:45971] - Marking node(s) as UNREACHABLE [Member(address = akka://[email protected]:2552, status = Leaving), Member(address = akka://[email protected]:49837, status = Up)]. Node roles [dc-default]
...
[ERROR] [08/02/2018 15:21:59.516] [ClusterSystem-akka.remote.default-remote-dispatcher-8] [akka.remote.artery.Association(akka://ClusterSystem)] Outbound control stream to [akka://[email protected]:49837] failed. Restarting it. Handshake with [akka://[email protected]:49837] did not complete within 20000 ms (akka.remote.artery.OutboundHandshake$HandshakeTimeoutException: Handshake with [akka://[email protected]:49837] did not complete within 20000 ms)
Akka versions are:
akka-cluster-tools_2.12:2.5.13
akka-cluster-metrics_2.12:2.5.13
Update all samples Akka 2.6 and convert to Akka Typed (if relevant). Also revisit if the sample makes sense, adds value or should be removed.
Creating this as an overview, even though not all samples are located in this repository.
[JVM-3] - must handle updates from different nodes *** FAILED ***
[JVM-3] Set(LineItem [productId=1, title=Apples, quantity=7]) was not equal to Set(LineItem [productId=1, title=Apples, quantity=7], LineItem [productId=3, title=Bananas, quantity=4]) (ShoppingCartSpec.scala:91)
[JVM-2] - must handle updates from different nodes *** FAILED ***
[JVM-2] Set(LineItem [productId=1, title=Apples, quantity=7]) was not equal to Set(LineItem [productId=1, title=Apples, quantity=7], LineItem [productId=3, title=Bananas, quantity=4]) (ShoppingCartSpec.scala:91)
This documentation refers to a file but the file is missing.
From discussion in #54 (comment)
akka-sample-persistence-java/README.md would reference existing examples
ViewExample is missing.
https://github.com/akka/akka-samples/search?q=ViewExample.java&unscoped_q=ViewExample.java
The Travis CI build should test that documentation for each sample builds successfully.
Another Travis CI job could be added that runs sbt paradox in the docs-gen project. This would catch issues like #112.
use AbstractActor instead of deprecated UntypedActor
@ortigali would you be interested in fixing this ticket also, since you did such a great job with akka/akka#22258
https://git.io/fppNz Are this still actual?
java.lang.AssertionError: Expected class sample.cqrs.ShoppingCart$ItemAdded, found class sample.cqrs.ShoppingCart$ItemQuantityAdjusted (ItemQuantityAdjusted(cart-2,bar,18))
at akka.actor.testkit.typed.internal.TestProbeImpl.assertFail(TestProbeImpl.scala:386)
at akka.actor.testkit.typed.internal.TestProbeImpl.expectMessageClass_internal(TestProbeImpl.scala:232)
at akka.actor.testkit.typed.internal.TestProbeImpl.expectMessageClass(TestProbeImpl.scala:218)
at sample.cqrs.IntegrationTest.step03_shouldContinueEventProcessingFromOffset(IntegrationTest.java:186)
Sparked by #11, we should probably have pretty much the same sample that existed for PersistentView but using persistence query.
I have downloaded and run akka-sample-fsm-java. It seems that it does not seem to work. Here's my output:
Manie has picked up Chopstick4 andChopstick0 and starts to eat
Krasser has picked up Chopstick3 andChopstick4 and starts to eat
Boner has picked up Chopstick1 andChopstick2 and starts to eat
Klang has picked up Chopstick2 andChopstick3 and starts to eat
Ghosh has picked up Chopstick0 andChopstick1 and starts to eat
Note that both Manie and Krasser pick up Chopstick4 at the same time, Boner and Klang pick up Chopstick2 at the same time and so on.
I then compared this with the output of the Scala version which is different and appears to be correct:
Manie has picked up Chopstick5 and Chopstick1 and starts to eat
Klang has picked up Chopstick3 and Chopstick4 and starts to eat
Manie puts down his chopsticks and starts to think
Klang puts down his chopsticks and starts to think
Boner has picked up Chopstick2 and Chopstick3 and starts to eat
Krasser has picked up Chopstick4 and Chopstick5 and starts to eat
Krasser puts down his chopsticks and starts to think
Boner puts down his chopsticks and starts to think
Manie has picked up Chopstick5 and Chopstick1 and starts to eat
Klang has picked up Chopstick3 and Chopstick4 and starts to eat
Klang puts down his chopsticks and starts to think
Manie puts down his chopsticks and starts to think
Krasser has picked up Chopstick4 and Chopstick5 and starts to eat
Boner has picked up Chopstick2 and Chopstick3 and starts to eat
Krasser puts down his chopsticks and starts to think
Boner puts down his chopsticks and starts to think
I also placed a breakpoint into Hakker.firstChopstickDenied: it was never called
Therefore I think that this sample code is broken, or maybe my development environment is broken.
Two more observations:
mvn clean in the akka-sample-fsm-java directory, which failed. Maybe there is an issue with the pom.xml?Complete log file is attached.
akka-fsm-java.log
Also look into what can we do for scalafmt conf files.
cleanupTask.cancel() should be added here
akka-sample-persistence-dc-java and akka-sample-persistence-dc-scala should be added to travis.yml and the lightbend credentials must be defined somehow.
@johanandren suggested this for the credentials: Encrypt a string and put into the travis.yml and then travis decrypts and sets an environment var with the decrypted value. I think that you can create the credentials programatically in the build file rather than pointing at a file on disk.
One thing to remember though, is that the build file must be a good template for those that are downloading the sample.
sbt has the dependency of leveldb with 0.7 which missed in maven.
I've tried to implement the akka sample, actor cluster simple which can be found here: http://www.lightbend.com/activator/template/akka-sample-cluster-java#code/src/main/resources/application.conf
I believe my directory structure is ok: src > main > resources > application.conf.
However, when I try to run the application I get this exception: "ActorSystem [akka://ClusterSystem] needs to have a 'ClusterActorRefProvider' enabled in the configuration".
My application.conf file is the same as in the example.
As reported in the forums: https://discuss.lightbend.com/t/supervision-java-example-wrong/5268
Looks like the sample has supervision declared in the wrong places, perhaps the FlakyExpressionCalculator initially did spawn children.
Start cluster on port(s) [2551, 2552, 0]
Exception in thread "main" com.typesafe.config.ConfigException$UnresolvedSubstitution: reference.conf @ jar:file:/C:/Users/Administrator/.m2/repository/com/typesafe/akka/akka-remote_2.12/2.5.9/akka-remote_2.12-2.5.9.jar!/reference.conf: 846: Could not resolve substitution to a value: ${akka.stream.materializer}
at com.typesafe.config.impl.ConfigReference.resolveSubstitutions(ConfigReference.java:111)
at com.typesafe.config.impl.ResolveContext.realResolve(ResolveContext.java:179)
at com.typesafe.config.impl.ResolveContext.resolve(ResolveContext.java:142)
at com.typesafe.config.impl.SimpleConfigObject$ResolveModifier.modifyChildMayThrow(SimpleConfigObject.java:379)
at com.typesafe.config.impl.SimpleConfigObject.modifyMayThrow(SimpleConfigObject.java:312)
at com.typesafe.config.impl.SimpleConfigObject.resolveSubstitutions(SimpleConfigObject.java:398)
at com.typesafe.config.impl.ResolveContext.realResolve(ResolveContext.java:179)
The receiveCommand method is implemented thus:
val receiveCommand: Receive = {
case Cmd(data) =>
persist(Evt(s"${data}-${numEvents}"))(updateState)
persist(Evt(s"${data}-${numEvents + 1}")) { event =>
updateState(event)
context.system.eventStream.publish(event)
}
case "snap" => saveSnapshot(state)
case "print" => println(state)
}
This line appears to be extraneous:
persist(Evt(s"${data}-${numEvents}"))(updateState)
It results in the examples' displaying this when run:
List(foo-0, foo-1, baz-2, baz-3, bar-4, bar-5, buzz-6, buzz-7)
Not only does this seem wrong, but it doesn't match the documentation here:
I find Cluster Sharding hard to understand. An example would be great.
Cont from akka/akka#16703
System: Linux mint 19 with 4.15 kernel
I cannot fully run the transformation example. The problem is, I can launch two process, they cost around 100MB space of /dev/shm. And when I launch the third process, the usage of /dev/shm increses to 900MB. Further, when I try to launch the fourth process, it just eats all my space and throws an error:
[info] Warning: space is running low in /dev/shm (tmpfs) threshold=167,772,160 usable=95,424,512
[info] Warning: space is running low in /dev/shm (tmpfs) threshold=167,772,160 usable=45,088,768
[info] [ERROR] [11/05/2018 21:03:56.156] [ClusterSystem-akka.actor.default-dispatcher-12] [akka://[email protected]:57246/] swallowing exception during message send
[info] io.aeron.exceptions.RegistrationException: IllegalStateException : Insufficient usable storage for new log of length=50335744 in /dev/shm (tmpfs)
[info] at io.aeron.ClientConductor.onError(ClientConductor.java:174)
[info] at io.aeron.DriverEventsAdapter.onMessage(DriverEventsAdapter.java:81)
[info] at org.agrona.concurrent.broadcast.CopyBroadcastReceiver.receive(CopyBroadcastReceiver.java:100)
[info] at io.aeron.DriverEventsAdapter.receive(DriverEventsAdapter.java:56)
[info] at io.aeron.ClientConductor.service(ClientConductor.java:660)
[info] at io.aeron.ClientConductor.awaitResponse(ClientConductor.java:696)
[info] at io.aeron.ClientConductor.addPublication(ClientConductor.java:371)
[info] at io.aeron.Aeron.addPublication(Aeron.java:259)
[info] at akka.remote.artery.aeron.AeronSink$$anon$1.<init>(AeronSink.scala:103)
[info] at akka.remote.artery.aeron.AeronSink.createLogicAndMaterializedValue(AeronSink.scala:100)
[info] at akka.stream.impl.GraphStageIsland.materializeAtomic(PhasedFusingActorMaterializer.scala:630)
[info] at akka.stream.impl.PhasedFusingActorMaterializer.materialize(PhasedFusingActorMaterializer.scala:450)
[info] at akka.stream.impl.PhasedFusingActorMaterializer.materialize(PhasedFusingActorMaterializer.scala:415)
[info] at akka.stream.impl.PhasedFusingActorMaterializer.materialize(PhasedFusingActorMaterializer.scala:406)
[info] at akka.stream.scaladsl.RunnableGraph.run(Flow.scala:588)
[info] at akka.remote.artery.Association.runOutboundOrdinaryMessagesStream(Association.scala:726)
[info] at akka.remote.artery.Association.runOutboundStreams(Association.scala:657)
[info] at akka.remote.artery.Association.associate(Association.scala:649)
[info] at akka.remote.artery.AssociationRegistry.association(Association.scala:989)
[info] at akka.remote.artery.ArteryTransport.association(ArteryTransport.scala:724)
[info] at akka.remote.artery.ArteryTransport.send(ArteryTransport.scala:710)
[info] at akka.remote.RemoteActorRef.$bang(RemoteActorRefProvider.scala:591)
[info] at akka.actor.ActorRef.tell(ActorRef.scala:124)
[info] at akka.actor.ActorSelection$.rec$1(ActorSelection.scala:265)
[info] at akka.actor.ActorSelection$.deliverSelection(ActorSelection.scala:269)
[info] at akka.actor.ActorSelection.tell(ActorSelection.scala:46)
[info] at akka.actor.ScalaActorSelection.$bang(ActorSelection.scala:280)
[info] at akka.actor.ScalaActorSelection.$bang$(ActorSelection.scala:280)
[info] at akka.actor.ActorSelection$$anon$1.$bang(ActorSelection.scala:198)
[info] at akka.cluster.ClusterCoreDaemon.gossipTo(ClusterDaemon.scala:1330)
[info] at akka.cluster.ClusterCoreDaemon.gossip(ClusterDaemon.scala:1047)
[info] at akka.cluster.ClusterCoreDaemon.gossipTick(ClusterDaemon.scala:1010)
[info] at akka.cluster.ClusterCoreDaemon$$anonfun$initialized$1.applyOrElse(ClusterDaemon.scala:496)
[info] at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171)
[info] at akka.actor.Actor.aroundReceive(Actor.scala:517)
[info] at akka.actor.Actor.aroundReceive$(Actor.scala:515)
[info] at akka.cluster.ClusterCoreDaemon.aroundReceive(ClusterDaemon.scala:295)
[info] at akka.actor.ActorCell.receiveMessage(ActorCell.scala:588)
[info] at akka.actor.ActorCell.invoke(ActorCell.scala:557)
[info] at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258)
[info] at akka.dispatch.Mailbox.run(Mailbox.scala:225)
[info] at akka.dispatch.Mailbox.exec(Mailbox.scala:235)
[info] at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
[info] at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
[info] at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
[info] at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Then all processes die. So my question is why it needs so much space? I have tested multiple times. It doesn't matter which process I launch, frontend or backend. They just eat significantly more space than the former one.
1: eat a little - some KBs
2: eat a little bit more - some MBs
3: eat a huge - some hundread MBs
4: don't know how much is enough
Both akka-sample-persistence-scala and akka-sample-persistence-java throws error as followings:
"无效的参数" means invalid argument.
yang@yang-VirtualBox:~/E/scalaProj/akka-samples/akka-sample-persistence-java$ sbt run
[info] Loading global plugins from /home/yang/.sbt/0.13/plugins
[info] Loading project definition from /home/yang/E/scalaProj/akka-samples/akka-sample-persistence-java/project
[info] Updating {file:/home/yang/E/scalaProj/akka-samples/akka-sample-persistence-java/project/}akka-sample-persistence-java-build...
[info] Resolving org.fusesource.jansi#jansi;1.4 ...
[info] Done updating.
[info] Set current project to akka-sample-persistence-java (in build file:/home/yang/E/scalaProj/akka-samples/akka-sample-persistence-java/)
[info] Updating {file:/home/yang/E/scalaProj/akka-samples/akka-sample-persistence-java/}akka-sample-persistence-java...
[info] Resolving jline#jline;2.14.3 ...
[info] Done updating.
[info] Compiling 3 Java sources to /home/yang/E/scalaProj/akka-samples/akka-sample-persistence-java/target/scala-2.12/classes...
[warn] Multiple main classes detected. Run 'show discoveredMainClasses' to see the list
Multiple main classes detected, select one to run:
[1] sample.persistence.PersistentActorExample
[2] sample.persistence.PersistentActorFailureExample
[3] sample.persistence.SnapshotExample
Enter number: 1
[info] Running sample.persistence.PersistentActorExample
[ERROR] [10/10/2017 09:57:52.140] [example-akka.actor.default-dispatcher-2] [akka://example/system/akka.persistence.journal.leveldb] 无效的参数
akka.actor.ActorInitializationException: akka://example/system/akka.persistence.journal.leveldb: exception during creation
at akka.actor.ActorInitializationException$.apply(Actor.scala:191)
at akka.actor.ActorCell.create(ActorCell.scala:608)
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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: 无效的参数
at sun.nio.ch.FileChannelImpl.map0(Native Method)
at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:926)
at org.iq80.leveldb.impl.MMapLogWriter.<init>(MMapLogWriter.java:63)
at org.iq80.leveldb.impl.Logs.createLogWriter(Logs.java:36)
at org.iq80.leveldb.impl.VersionSet.initializeIfNeeded(VersionSet.java:106)
at org.iq80.leveldb.impl.VersionSet.<init>(VersionSet.java:91)
at org.iq80.leveldb.impl.DbImpl.<init>(DbImpl.java:178)
at org.iq80.leveldb.impl.Iq80DBFactory.open(Iq80DBFactory.java:59)
at akka.persistence.journal.leveldb.LeveldbStore.preStart(LeveldbStore.scala:178)
at akka.persistence.journal.leveldb.LeveldbStore.preStart$(LeveldbStore.scala:177)
at akka.persistence.journal.leveldb.LeveldbJournal.preStart(LeveldbJournal.scala:23)
at akka.actor.Actor.aroundPreStart(Actor.scala:522)
at akka.actor.Actor.aroundPreStart$(Actor.scala:522)
at akka.persistence.journal.leveldb.LeveldbJournal.aroundPreStart(LeveldbJournal.scala:23)
at akka.actor.ActorCell.create(ActorCell.scala:591)
... 7 more
When the consistent hashing router is completed akka/akka#27729 we should update the cluster samples to use that for the Worker routing
https://github.com/akka/akka-samples/pull/137/files#r341505873
Hi,
Method reference state::update is not working in java persistent example PersistentActorExample.java:
@Override
public Receive createReceiveRecover() {
return receiveBuilder()
.match(Evt.class, state::update)
.match(SnapshotOffer.class, ss -> state = (ExampleState) ss.snapshot())
.build();
}Seems like Method reference doesn't work with ReceiveBuilder.match()
The first run result is [foo-0, foo-1, baz-2, baz-3, bar-4, bar-5, buzz-6, buzz-7].
The second run result is [foo-0, foo-1, baz-2, baz-3, bar-4, bar-5, foo-6, foo-7, baz-8, baz-9, bar-10, bar-11, buzz-12, buzz-13], which only recovered the snapshot but not any younger events. The result should be [foo-0, foo-1, baz-2, baz-3, bar-4, bar-5, buzz-6, buzz-7, foo-8, foo-9, baz-10, baz-11, bar-12, bar-13, buzz-14, buzz-15].
Hi,
I have been trying to run the camel samples java and scala, using openjdk8 and sbt 0.13.13
Both the samples fail to start the application and allow me to view the akka page on browser
Executing the sample i receive the below logs
[ERROR] [SECURITY][08/04/2017 02:40:38.015] [some-system-akka.actor.default-dispatcher-6] [akka.actor.ActorSystemImpl(some-system)] Uncaught error from thread [some-system-akka.actor.default-dispatcher-6]: org.apache.camel.impl.HeaderFilterStrategyComponent: method <init>()V not found, shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[some-system]
java.lang.NoSuchMethodError: org.apache.camel.impl.HeaderFilterStrategyComponent: method <init>()V not found
Some help on this would be very helpful
CassandraSessionExtension is used for the read side but built from the journal configuration. It might be more clear to decouple the config (even if they’re initialized from the same defaults for demo purposes) and name it something like CassandraReadSideSessionExtension.
In fact, it doesn’t show how to configure the database at all, it just relies on defaults, so readers might find it difficult it to apply this to their real applications.
It doesn’t exactly demonstrate CQRS, because the event processor only logs events, and doesn’t update a read model. It would be nice to demonstrate how to implement an actual read model, if only to show that there’s little magic to it (just update and query the database using CQL). I’ve seen some people confused by this, expecting some specific API for the read-side queries. Would also help demonstrate the context for how CQRS is used. Might be awkward to do as a pure command-line app, however. An Akka HTTP API server might be a more realistic example.
Unclear why it has this after-persist callback:
persist(SwitchCreated(nPorts)) {
e => portStatus = createSwitch(nPorts)
}
Updating portStatus is (and should be) handled by the event handler. Similar for SetPortStatus.
Why not use become to model the before/after creation states and switch between command handlers? That’s closer to how we recommend people use the typed API, so will help make an easier transition.
portStatus is an Option[Map[Int, Boolean]] but seems like it would be more natural as Option[IndexedSeq[Int, Boolean]] or similar, since the port numbers are contiguous ordinals and the map is populated eagerly in createSwitch. For that matter, nothing ever reads the values, so the state could just be modelled as portCount: Option[Int], which might be more in keeping with pure CQRS. OTOH, maybe it could include logic to avoid emitting a PortStatusSet event when it receives a command to set a port to its existing status value, in which case it would need to retain them.
Could have more comments overall, explaining the purpose of different parts, especially in the EventProcessor. Also, to clarify that the event processor handles each event at least once and duplicates may occur.
The README says “The implementation is resilient: it uses an Akka Cluster Singleton in combination with Akka Cluster Sharding.” I think it could elaborate on how it handles various failure conditions. That will help show how these tools enable building resilient services.
as we're using tech hub now
Akka Samples on 2.6 branch
sbt "runMain sample.DiningHakkers" should startup and run FSM Scala sample application with relevant log messages displaying to console.
akka-sample-fsm-scala application fails to log messages.
The following runtime exception is thrown:
12:14:53,585 |-ERROR in ch.qos.logback.core.joran.event.SaxEventRecorder@584740ac - XML_PARSING - Parsing fatal error on line 19 and column 1
12:14:53,585 |-ERROR in ch.qos.logback.core.joran.event.SaxEventRecorder@584740ac - org.xml.sax.SAXParseException; systemId: jar:file:/var/folders/b3/cwcv8rkd4bj_5yfy02zt7zz80000gn/T/sbt_b7e7506a/job-1/target/0337a9d7/akka-sample-fsm-scala_2.13-HEAD+20191230-1214.jar!/logback.xml; lineNumber: 19; columnNumber: 1; XML document structures must start and end within the same entity.
Create new FSM Example project (Scala)
Run sbt "runMain sample.DiningHakkers"
Observe XML_PARSING Error being thrown upon startup.
PR to follow
Would be nice to have a samples of the logging capabilities with some variety.
It takes a bit longer to search libs to configure the logger. Would be nice if existing samples or new will be introduced for this purposes.
Hello,
I pulled the akka-sample-cluster-scala project
https://github.com/akka/akka-samples/tree/2.5/akka-sample-cluster-scala
and ran [sbt "runMain sample.cluster.simple.SimpleClusterApp"] and I got the error messages below.
Any advice for me?
I ran
sbt "runMain sample.cluster.simple.SimpleClusterApp 2551"
sbt "runMain sample.cluster.simple.SimpleClusterApp 2552"
sbt "runMain sample.cluster.simple.SimpleClusterApp 0"
The result is same.
I am using a MacBookPro, mojave osx. I am using oracle java version 8.171
Thank you,
cosmir17
sbt "runMain sample.cluster.simple.SimpleClusterApp"
[info] Loading settings for project global-plugins from idea.sbt ...
[info] Loading global plugins from /Users/sk/.sbt/1.0/plugins
[info] Loading settings for project akka-sample-cluster-scala-build from plugins.sbt ...
[info] Loading project definition from /Users/sk/IdeaProjects/akka-samples/akka-sample-cluster-scala/project
[info] Loading settings for project akka-sample-cluster-scala from build.sbt ...
[info] Set current project to akka-sample-cluster-scala (in build file:/Users/sk/IdeaProjects/akka-samples/akka-sample-cluster-scala/)
[info] Updating ...
[info] Done updating.
[warn] Multiple main classes detected. Run 'show discoveredMainClasses' to see the list
[info] Packaging /Users/sk/IdeaProjects/akka-samples/akka-sample-cluster-scala/target/scala-2.12/akka-sample-cluster-scala_2.12-fec5470d.jar ...
[info] Done packaging.
[info] Running (fork) sample.cluster.simple.SimpleClusterApp
[info] [INFO] [01/25/2019 22:53:44.304] [main] [akka.remote.artery.tcp.ArteryTcpTransport(akka://ClusterSystem)] Remoting started with transport [Artery tcp]; listening on address [akka://[email protected]:49529] with UID [-2464032911652136694]
[info] [INFO] [01/25/2019 22:53:44.325] [main] [akka.cluster.Cluster(akka://ClusterSystem)] Cluster Node [akka://[email protected]:49529] - Starting up, Akka version [2.5.18] ...
[info] [INFO] [01/25/2019 22:53:44.446] [main] [akka.cluster.Cluster(akka://ClusterSystem)] Cluster Node [akka://[email protected]:49529] - Registered cluster JMX MBean [akka:type=Cluster]
[info] [INFO] [01/25/2019 22:53:44.446] [main] [akka.cluster.Cluster(akka://ClusterSystem)] Cluster Node [akka://[email protected]:49529] - Started up successfully
[info] [WARN] [01/25/2019 22:53:44.487] [ClusterSystem-akka.actor.default-dispatcher-3] [akka://[email protected]:49529/system/cluster/core/daemon/downingProvider] Don't use auto-down feature of Akka Cluster in production. See 'Auto-downing (DO NOT USE)' section of Akka Cluster documentation.
[info] [ERROR] [01/25/2019 22:53:44.521] [ClusterSystem-akka.actor.default-dispatcher-11] [akka.cluster.ClusterActorRefProvider] No root guardian at [akka.tcp://[email protected]:2551]
[info] java.lang.IllegalArgumentException: Wrong protocol of [akka.tcp://[email protected]:2551/], expected [akka]
[info] at akka.remote.RemoteActorRef.<init>(RemoteActorRefProvider.scala:533)
[info] at akka.remote.RemoteActorRefProvider.rootGuardianAt(RemoteActorRefProvider.scala:378)
[info] at akka.actor.ActorRefFactory.actorSelection(ActorRefProvider.scala:351)
[info] at akka.actor.ActorRefFactory.actorSelection$(ActorRefProvider.scala:345)
[info] at akka.actor.ActorCell.actorSelection(ActorCell.scala:431)
[info] at akka.cluster.JoinSeedNodeProcess$$anonfun$receive$4.$anonfun$applyOrElse$7(ClusterDaemon.scala:1562)
[info] at akka.cluster.JoinSeedNodeProcess$$anonfun$receive$4.$anonfun$applyOrElse$7$adapted(ClusterDaemon.scala:1562)
[info] at scala.collection.immutable.Set$Set2.foreach(Set.scala:130)
[info] at akka.cluster.JoinSeedNodeProcess$$anonfun$receive$4.applyOrElse(ClusterDaemon.scala:1562)
[info] at akka.actor.Actor.aroundReceive(Actor.scala:517)
[info] at akka.actor.Actor.aroundReceive$(Actor.scala:515)
[info] at akka.cluster.JoinSeedNodeProcess.aroundReceive(ClusterDaemon.scala:1535)
[info] at akka.actor.ActorCell.receiveMessage(ActorCell.scala:588)
[info] at akka.actor.ActorCell.invoke(ActorCell.scala:557)
[info] at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258)
[info] at akka.dispatch.Mailbox.run(Mailbox.scala:225)
[info] at akka.dispatch.Mailbox.exec(Mailbox.scala:235)
[info] at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
[info] at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
[info] at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
[info] at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
[info] [INFO] [01/25/2019 22:53:44.525] [ClusterSystem-akka.actor.default-dispatcher-2] [akka.tcp://[email protected]:2551/] Message [akka.cluster.InternalClusterAction$InitJoin] from Actor[akka://ClusterSystem/system/cluster/core/daemon/joinSeedNodeProcess-1#1069204917] to Actor[akka.tcp://[email protected]:2551/] was not delivered. [1] dead letters encountered. If this is not an expected behavior, then [Actor[akka.tcp://[email protected]:2551/]] may have terminated unexpectedly, This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [ERROR] [01/25/2019 22:53:44.525] [ClusterSystem-akka.actor.default-dispatcher-11] [akka.cluster.ClusterActorRefProvider] No root guardian at [akka.tcp://[email protected]:2552]
[info] java.lang.IllegalArgumentException: Wrong protocol of [akka.tcp://[email protected]:2552/], expected [akka]
[info] at akka.remote.RemoteActorRef.<init>(RemoteActorRefProvider.scala:533)
[info] at akka.remote.RemoteActorRefProvider.rootGuardianAt(RemoteActorRefProvider.scala:378)
[info] at akka.actor.ActorRefFactory.actorSelection(ActorRefProvider.scala:351)
The main branch is the 2.5 branch, but we also still have a 'master' branch lying around. That confuses me from time to time. Perhaps we should just remove it?
Akka Cluster Sample Example With Protobuf messaging.
Currently, the serialization that we use to serialize Akka messages is by default java serialization, and protobuf is a go-to if we want to serialize, Can we have a example with akka-cluster-sample with protobuf. I've created one, https://github.com/shankarshastri/akka-cluster-example-protocol-buffer
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.