Re: [akka-user] Why is aroundReceive protected[akka]?

On Wed, Oct 21, 2015 at 1:18 AM, Patrik Nordwall wrote: > It's not in 2.3 > Okay -- that's what I thought, from trying to find it in the docs. In which case, once I'm upgraded to 2.4 (hopefully soonish), I'll upgrade Requester to use that and see if everything goes

Re: [akka-user] Combine FSM[S, D] and DiagnosticActorLogging

I have no ideas of how to solve that. We should probably not have defined `log` in `FSM` but its too late to change that. /Patrik On Mon, Oct 12, 2015 at 11:18 AM, Michael Zinsmaier < michael.zinsma...@googlemail.com> wrote: > Hi Patrik, > > I tried your suggestion, unfortunately I get the same

Re: [akka-user] Messages being loss on an Akka Cluster

What version of Akka are you using? How do you send the messages? Is it direct message sends with ActorRef or are you using any of the cluster tools, such as Cluster Sharding? What total throughput are we talking about? 64* 100 msg/s ? Do you see any pattern of when the messages are lost, e.g. is

Re: [akka-user] is akka.actor.ActorNotFound possible after context.actorOf(...)?

Yes, I think that is possible for remote deployed actors. Actor creation is asynchronous. /Patrik On Wed, Oct 14, 2015 at 5:50 PM, Kostas kougios < kostas.koug...@googlemail.com> wrote: > I've been debugging this issue for a couple of days now. I am getting an > akka.actor.ActorNotFound after

Re: [akka-user] Modeling synchronous startup behavior

For posterity, I ended up doing this, and now i'm assured that the constructor ran and I didn't have to add any ad hoc messages... class MyActor(p: Promise[ActorRef]) extends Actor { override def preStart() { p.complete(Success(self)) } override def receive = {

Re: [akka-user] Akka Cluster seed node config for restarts

I've create the issue here: https://github.com/akka/akka/issues/18757 I was told that I didn't have write permission to attach documents. Do you know how I can go about getting that permission? For now I just inlined the logs in the issue text. Thanks, Gary On Wednesday, October 21, 2015

Re: [akka-user] Re: Detecting Quarantined state

I've logged the issue here: https://github.com/akka/akka/issues/18758 Thanks, Gary On Wednesday, October 21, 2015 at 8:21:10 AM UTC-7, Patrik Nordwall wrote: > > > > On Tue, Oct 20, 2015 at 9:06 PM, Gary Wu > wrote: > >> I'm also interested in this. Have you found a good

Re: [akka-user] Persistence of dynamic hierarchy of actors with short/medium length of life

Yup, intent based approach makes it tick. I've already applied it successfully to the project.  Btw, I guess this is something other developers may bump into as well, would you be up to documenting this pattern? Either as part of the documentation or as a blog maybe? I fear intent hell now

Re: [akka-user] Persistence of dynamic hierarchy of actors with short/medium length of life

Hi Konrad, Yup, intent based approach makes it tick. I've already applied it successfully to the project. I fear intent hell now :-). Robert -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

Re: [akka-user] Persistence of dynamic hierarchy of actors with short/medium length of life

Hi Konrad, Yup, intent based approach makes it tick. I've already applied it successfully to the project. I fear intent hell now :-). On Fri, Oct 9, 2015 at 10:59 PM, Konrad Malawski wrote: > Hi Robert, > In order to get this right you'll need to pivot your thinking about >

[akka-user] Spray 1.3.3 and Aka 2.4

Is this possible? I've learned that migration from Spray to Akka HTTP is not always trivial, and that the performance is not yet there, but would like to benefit from the other goodies in 2.4. Thanks. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ:

[akka-user] How to scale up or out persistent actor for better throughput

Hi, Is it possible to use persistent actor with router such as to scale out. If you have elasticity with persistent actor you have a problem with your event sourcing. Hence i wonder how to scale up or out persistent actors for better throughput ? Best, M -- >> Read the

Re: [akka-user] Spray 1.3.3 and Aka 2.4

2.4 and 2.3 are binary compatible, so you can just give it a try with 2.4.0 :) Happy hakking! --  Cheers, Konrad 'ktoso’ Malawski Akka @ Typesafe On 21 October 2015 at 23:19:20, Richard Rodseth (rrods...@gmail.com) wrote: Is this possible? I've learned that migration from Spray to Akka HTTP

[akka-user] How to delete all the messages in the mailbox when actor is kiiled?

Hi All, I am trying to learn Akka. I am trying out the Supervisor concept in Akka. I see from the docs that when an Actor is killed using the "Kill" message, it throws ActorKilledException. So, I am handling this exception in Supervisor and restarting the Actor in Supervisor code. But all the

[akka-user] Re: How to scale up or out persistent actor for better throughput

You can use persistentAsync call instead persistent call within persistent actor in points you can have a smaller consistency level. What journal plugin you are using? What are your throughput requeriments? On Wednesday, October 21, 2015 at 9:29:26 PM UTC, Maatary Okouya wrote: > > Hi, > > Is

[akka-user] Re: How to scale up or out persistent actor for better throughput

I forgot say, persistAsync performs batch insertion under high load to optimize throughput On Wednesday, October 21, 2015 at 9:29:26 PM UTC, Maatary Okouya wrote: > > Hi, > > Is it possible to use persistent actor with router such as to scale out. > If you have elasticity with persistent

Re: [akka-user] How to scale up or out persistent actor for better throughput

Maatary – please do not cross post right away to multiple spots, it makes it really hard to track what's been answered and what not. If after a longer time you don't get a reply somewhere it's ok to cross post, for more exposure, however then please do link back to the answer you get somewhere

Re: [akka-user] How to scale up or out persistent actor for better throughput

Konrad understood thanks for the initial reply. On Wed, Oct 21, 2015 at 7:51 PM Konrad Malawski < konrad.malaw...@typesafe.com> wrote: > Maatary – *please* do not cross post right away to multiple spots, it > makes it really hard to track what's been answered and what not. > If after a longer

[akka-user] Re: Changing protocol's case classes

Use protobuf, it support schema evolution very well. Em quarta-feira, 21 de outubro de 2015 08:33:52 UTC-3, Lap Ming Lee escreveu: > > Let's say I have an API gateway that talks to database micro services > which have version 0. > > And in version 0, the query takes a case class with 3

[akka-user] Re: Integration tests with Stubbed Cassandra

Hi Anders, You might want to have a look into this [1]. I've used its Cassandra embedded server in several ocassions, e.g. [2]. Hope this helps. [1] https://github.com/Sphonic/sphonic-phantom [2] https://github.com/Tecsisa/reactive-cassandra-phantom El martes, 20 de octubre de 2015, 15:00:59

[akka-user] Changing protocol's case classes

Let's say I have an API gateway that talks to database micro services which have version 0. And in version 0, the query takes a case class with 3 parameters like so: case class Query(param1: String, param2: Int, param3: Long) I want to know what happens when I change the under of params in

Re: [akka-user] AllocationStrategy rebalance() is stopping actors outside resharding list

ah, thanks for the update. Note that in Akka 2.4.0 the allocation strategy is async (returning a Future) and that might make it easier for you to integrate with actors. /Patrik On Wed, Oct 21, 2015 at 2:28 PM, Eduardo Fernandes wrote: > Ha my fault! > > I didn't know that

Re: [akka-user] Akka Customers

> 20 okt 2015 kl. 22:55 skrev Harit Himanshu : > > Hello > > I am introducing Akka framework in my company and as part of presentation to > Management, I have to add a slide telling them which companies are already > using it. > > Is there a comprehensive list

Re: [akka-user] Akka Cluster seed node config for restarts

Hi Gary, It should be able to join the other nodes, but if it fails for some reason within a timeout it will join itself. The timeout is configured by akka.cluster.seed-node-timeout and is by default 5 seconds. I find it strange that you would not be able to get a reply from the other seed nodes