Re: [akka-user] Re: What's the replacement for Akka Actor Publisher and Subscriber?

2016-10-13 Thread Viktor Klang
RS Backpressure can piggyback on top of TCP, which means HTTP, WebSocket and HTTP/2 support. Besides that there's *tons* of integrations (Sources and Sinks) for networked components. As if that wasn't enough there's both the ReactiveSocket initiative ( http://reactivesocket.io/) as well as Apache

[akka-user] Re: What's the replacement for Akka Actor Publisher and Subscriber?

2016-10-13 Thread Dagny T
HOLD ON .. SERIOUSLY?! So, do I understand correctly that the 'Reactive Manifesto' industry coalition among leading thought leaders at Netflix, Pivotal, and Lightbend; is for all intents and purposes -- still under construction? Sorry; I'm just seeking straight answers on this to gauge if

[akka-user] Re: Replaying journal events without actually recovering Actors?

2016-10-13 Thread Spencer Judge
I can answered my own question here. It pretty much just came down to my lack of knowledge around the streams API, which I hadn't used yet. Changing the test to this works perfectly: test("test journal backwards compatibility", EndToEndTest) { val readJournal =

[akka-user] Akka stream - Flow in Pause

2016-10-13 Thread regis leray
Hi, I'm trying to implements a way to control a flow (start/stop), nothing was implemented yet in the core of akka-stream My current implementation looks like this. trait ValveSwitch { def open: Unit def close: Unit } class Valve[A](mode: ValveMode = ValveMode.Open) extends

Re: [akka-user] Testing Akka Persistence Recovery

2016-10-13 Thread Richard Rodseth
Thank you. That did the trick. watch(subscriber1) system.stop(subscriber1) expectTerminated(subscriber1) val subscriber2 = system.actorOf(props1, "name1") // New actor, same name subscriber2 ! Subscriber.GetState val result2 = expectMsg(...something...) On

Re: [akka-user] Testing Akka Persistence Recovery

2016-10-13 Thread Patrik Nordwall
On Thu, Oct 13, 2016 at 11:08 AM, Sebastian Piu wrote: > Is there any way of simulating the failure while processing, or force > terminate the actor? > There is a akka.actor.Kill message that will make the Actor throw an ActorKilledException, which will trigger

Re: [akka-user] Testing Akka Persistence Recovery

2016-10-13 Thread Sebastian Piu
Is there any way of simulating the failure while processing, or force terminate the actor? It if my understanding that stopping will do it after the current message finishes right? On Thu, 13 Oct 2016, 08:01 Patrik Nordwall, wrote: > The actor's name and

Re: [akka-user] Testing Akka Persistence Recovery

2016-10-13 Thread Patrik Nordwall
The actor's name and persistenceId doesn't have to be the same, but if you need that you must wait until it has been terminated before starting the new instance watch(subscriber1) expectTerminated(subscriber2) On Thu, Oct 13, 2016 at 7:10 AM, Richard Rodseth wrote: >

Re: [akka-user] Missing api GraphStageLogic

2016-10-13 Thread Viktor Klang
by default scaladoc only shows public members and the methods you are speaking of are protected, so you need to click "All" -- Cheers, √ On Oct 13, 2016 8:37 AM, "Ortigali Bazarov" wrote: > In documentation, there is a example how to use GraphStageLogic's pull, >

[akka-user] Re: Missing api GraphStageLogic

2016-10-13 Thread Tal Pressman
Just change the visibility from 'public' to 'all' Tal On Thursday, October 13, 2016 at 9:37:41 AM UTC+3, Ortigali Bazarov wrote: > > In documentation, there is a example how to use GraphStageLogic's pull, > push, emit and etc methods. But when i looked for their's signature in > here >

[akka-user] Missing api GraphStageLogic

2016-10-13 Thread Ortigali Bazarov
In documentation, there is a example how to use GraphStageLogic's pull, push, emit and etc methods. But when i looked for their's signature in here i could not find these methods. --