I have the same issue with
http://stackoverflow.com/questions/29589909/akka-cluster-memberup-message-from-dead-letters-not-delivered
But I don't see any reasonable explanation in the above post, can you help
me identify the root cause?
Thank you.
--
>> Read the docs:
Use deferAsync after persistAll
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message
Small observation - messages start deliver to the "processor" node only
when I send a lot of them (like ~ 20 per second). Looks like some kind of
buffer involved in the problem, but I'm not sure.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>>
On 13/04/17 11:41, Martynas Mickevičius wrote:
we—the Akka committers—are proud to be able to announce the availability of
Akka 2.5.0.
I've updated my dependencies to 2.5.0:
libraryDependencies ++= Seq(
"com.typesafe.akka" %% "akka-actor" % "2.5.0",
"com.typesafe.akka" %%
Congrats on the release of 2.5.
Isn't the documentation and accompanying sample for Resumable Projections a
bit odd?
http://doc.akka.io/docs/akka/2.5.0/scala/persistence-query.html#Resumable_projections
I just realized that I have been misusing PersistentActor.persistAll() for
quite some time now -- the only reason it hasn't produced horrible bugs is
because I haven't yet used it for more than a single Event at a time. (And
foolishly didn't check my types properly.) I had assumed it called its
Hi, I'm trying to configure a simple Akka cluster-aware router group, using
2 nodes ("receiver" and "processor" roles).
Everything configured in code.
on RECEIVER node:
List path = singletonList("/user/processorRouter");
processorRouter = context().actorOf(
new ClusterRouterGroup(new
Both http servers (jetty and akka-http) will try to bind to the
specified port (9001) and the OS will only allow the first one to
succeed, leading to the exception you are seeing in the process that is
second to start.
If you must have them serve requests on the same port, then the way I
see
Hey folks,
I've used AKKA Camel for HTTP service...
It's endpoint is "jetty:http://0.0.0.0:9001/test;
and recently I figured out that AKKA-HTTP is easy and fun.
So I tried bind akka-http route("http://0.0.0.0:9001/hi on same port.
val route =
path("hi") {
get {
complete("hello")
