[akka-user] AKKA-Message delivery guarantee

Hi Team, I am trying to insert 20k records into database using AKKA.But I found only 19,994 records being inserted and rest 6 records were failure.Is there any way in AKKA that I can get a solution for this i.e I need all the 20k records to be inserted into DB without failure? -- >

[akka-user] Re: akka cluster - verbosity of logging on node exit

Also I think the first of those log lines should be at the DEBUG level, since shortly after this INFO logging happens: [Cluster(akka://mycluster)] Cluster Node [akka.tcp://mycluster@myhose:8402] - Leader is removing exiting node [akka.tcp://mycluster@myhose:30957] On Mon, Jul 21, 2014 at 11:10 A

[akka-user] akka cluster - verbosity of logging on node exit

When a node initiates a leave for itself, the exit is pretty verbose. i.e. these are logged on every cluster member [2014-07-21 05:36:23,181][INFO ][akka.dummy ] [Cluster(akka://mycluster)] Cluster Node [akka.tcp://mycluster@myhost:8402] - Marking exiting node(s) as UNREACHABLE [Mem

Re: [akka-user] akka cluster - oversized payloads

Thanks for the input Patrik. I've confirmed that the issue wasn't anything in the application by isolating it in a simple project , see Churn.scala . I set the paylo

Re: [akka-user] akka cluster - oversized payloads

We met this issue too. Shall we upgrade to 2.4 to resolve this? On Sunday, July 20, 2014 9:49:08 PM UTC+8, Patrik Nordwall wrote: > > Yes, it can be because of the many join/leave cycles and lack of vector > clock pruning. > > I agree that it is strange that the cluster is working after that, be

Re: [akka-user] Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

My pleasure! Feel free to ask any follow up questions :-) Happy hakking! On Sun, Jul 20, 2014 at 7:42 PM, Yann Le Moigne wrote: > Hi Konrad > > Yes it help ! > Thank you. > > For my first incursion in akka community, you was very helpfull and > reactive. > Thanks :) > > Le dimanche 20 juillet

Re: [akka-user] Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

Hi Konrad Yes it help ! Thank you. For my first incursion in akka community, you was very helpfull and reactive. Thanks :) Le dimanche 20 juillet 2014 18:42:12 UTC+2, Konrad Malawski a écrit : > > Without modifying the tested actor you could test (1) by sending an > Idenfity message to the sel

Re: [akka-user] Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

Without modifying the tested actor you could test (1) by sending an Idenfity message to the selection (testedGuy/*), and then expect exactly one ActorIdentity as response (expect it, and then expectNoMsg). I hope this helps! ​ On Sun, Jul 20, 2014 at 4:31 PM, Yann Le Moigne wrote: > I'm begin

Re: [akka-user] Akka Actor Per Request Java Sample

At least some of this code is necessarily in Scala as Spray does not support Java. You could likely get some of this working (or something approximating it) with the new akka-http module, but it does not yet have an equivalent for spray-routing, so you would have to manually handle the route constr

[akka-user] Re: Akka Actor Per Request Java Sample

Hello John, I don't think there is an equivalent repo to this out there... Although I assume you've seem this post http://techblog.net-a-porter.com/2013/12/ask-tell-and-per-request-actors/ where this code sample originates from? The concepts are pretty generic, and I would recommend checking out

Re: [akka-user] Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

I'm beginning, so nu much insight to make a whish at this time ; but of course, managed test & journal lifecycle by specialized TestKit sound great. I'm trying to switch to standard testing style, but I can't find a way to replace : 1: assert(actorRef.underlyingActor.context.children.size === 1)

Re: [akka-user] Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

Yes, I agree this should be mentioned explicitly - I have created this issue to track this: https://github.com/akka/akka/issues/15569 By the way, we are thinking of offering a TestKit for akka-persistence. I think it would be a neat addition (would make prepping journal state before your tests e

Re: [akka-user] Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

Ho, OK. Maybe this should be explicitly added to documentation ? Thanks for the answer. Le dimanche 20 juillet 2014 15:46:02 UTC+2, Konrad Malawski a écrit : > > Hi Yann, > TestActorRef is not compatible with Akka persistence. We discussed this in > this issue here: https://github.com/akka/akka

Re: [akka-user] akka cluster - oversized payloads

Yes, it can be because of the many join/leave cycles and lack of vector clock pruning. I agree that it is strange that the cluster is working after that, because the gossip message size will not shrink. The vector clocks only increase in size if the cluster membership state is modified by diff

Re: [akka-user] Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

Hi Yann, TestActorRef is not compatible with Akka persistence. We discussed this in this issue here: https://github.com/akka/akka/issues/15293 Please use traditional testing style with persistence (as in expect messages etc). -- Konrad 'ktoso' Malawski (Sent from my phone) On 20 Jul 2014 15:23,

[akka-user] Re: Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

Ok, I find "why" : Removing the testFixture fixed the problem. Le dimanche 20 juillet 2014 15:21:51 UTC+2, Yann Le Moigne a écrit : > > Hi, > > I'm trying to test a persistent actor > > class ServerManager extends PersistentActor { > override def persistenceId = "ServerManager" > > override de

[akka-user] Testing PersistentActor, receiveCommand is never called (Akka 2.3.4)

Hi, I'm trying to test a persistent actor class ServerManager extends PersistentActor { override def persistenceId = "ServerManager" override def receiveRecover: Receive = { case _ => } override def receiveCommand: Receive = { case Commands.Server.Watch(address) => persist(Event

Re: [akka-user] Why does akka-persistence not provide an API to read a specific entry from a journal?

Hi Moiz, 20 jul 2014 kl. 00:28 skrev Moiz Raja : > Ronald and Konrad. Firstly thanks for your responses. (I’m Roland, BTW ;-) ) > So, as it so happens I do want my actor to be persistent in the sense that I > do want to be able to shutdown my actor, restart it and have it back to the > state