[akka-user] count of all messages sent

is there any way to override tell method of actorref and maintain counter in override method to get count of al sent messages -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >>

Re: [akka-user] count of all messages sent

Thats more of a task for monitoring tools, i.e. our reactive monitoring than manually building the same :) https://www.typesafe.com/blog/introducing-reactive-monitoring-v1-0-beta-reactive-platform On Oct 29, 2015 23:03, "akkauser" wrote: > is there any way to override

Re: [akka-user] Cluster sharding with Persistence: Failing require statement,

Thanks for the update. For reference: Removal of Internal Cluster Sharding Data /Patrik On Thu, Oct 29, 2015 at 11:49 PM, Stefan Bleibinhaus < stefan.bleibinh...@gmail.com> wrote: >

Re: [akka-user] Re: [Akka Cluster 2.4] Rebalancing and Remember entities

Thanks for the update, and for sharing the solution. /Patrik On Thu, Oct 29, 2015 at 12:23 PM, Gabriel Volpe wrote: > Our BIG MISTAKE was that we totally forgot to read this simple lines of > the Cassandra Plugin's README file > > "This version of

Re: [akka-user] Re: Akka-Spray application losing messages

A few possible reasons: 1) Use latest stable Akka version, i.e. 2.4.0 or 2.3.14 2) Binding to hostname 0.0.0.0 is not supported 3) It may take a while until ClusterClient and the servers side receptionists knows about the target destinations, and then messages might be dropped You should look

Re: [akka-user] What does it means : notifying others about successful state changes by publishing events ?

On Sun, Oct 25, 2015 at 2:41 AM, Maatary Okouya wrote: > > Hi, > > > in the AKKA Doc on persistent actor, what is the purpose of < others about successful state changes by publishing events>> in: > > =>>The main responsibility of an event handler is changing persistent

[akka-user] akka-http, websockets, and cluster sharding

I have a web service that up until my addition of server-side web socket support, worked fine. I use akka-http to handle HTTP requests, and a cluster sharding region to route messages (sourced from the HTTP request) to actors that handle a particular "job" (the job id is the id used for