[akka-user] Akka Cluster seed node problem

Hi, I am working with akka distributed worker template available on typesafe. I am using it to write a backend job which takes data from siebel using soap calls and inserts in mongo. This job is supposed to run once a week for few hours. Based on the cluster-usage and other documentation on AK

[akka-user] Re: Sending message to Actor from Play Controller.

Not to worry, have been a bit silly, the controller wasn't sending the correct message: def multiply(num: Long) = Action { implicit request => implicit val timeout = Timeout(5.seconds) val frontend = core.Main.frontend val work = Work(nextWorkId(), num) frontend ! work Ok

[akka-user] Re: ANNOUNCE: First akka-http-core preview and updated akka-stream preview

Good news, well done all :-) Is there any further news about the impending replacement for spray-routing and the future of its use of shapeless HList? -- T On Friday, 27 June 2014 02:44:03 UTC-7, Björn Antonsson wrote: > > Dear Akka and Spray community, > > we are very happy and excited to rele

Re: [akka-user] Re: Inconsistencies in actorSelection resolving a remote actor

Hi, The reason is that your code checks directly if the Future has completed (which it most probably hasn't). You should either Await the completion of the Future, or do something on completion like this. actorRefFuture.onComplete(new OnComplete() {     @Override     public void onComplete(Thr

[akka-user] Re: ANNOUNCE: First akka-http-core preview and updated akka-stream preview

Congratulations guys! I had the chance to look trough the code a few days ago and was really surprised with how simple and concise it is, akka-http is (as Spray is also) a very interesting piece of engineering, keep up with the awesome work! -- >> Read the docs: http://akka.io/d

[akka-user] Sending message to Actor from Play Controller.

I have been playing with the distributed worker pattern and I'm running into an issue pushing work from a web request. The example project has a frontend: val mediator = DistributedPubSubExtension(context.system).mediator def receive = { case work => log.in

Re: [akka-user] ̣̣[akka-stream] Looping or recusrion in Duct / Flow

On Fri, Jun 27, 2014 at 12:23 PM, Endre Varga wrote: > > > > On Fri, Jun 27, 2014 at 11:59 AM, benq wrote: > >> >> >> Le vendredi 27 juin 2014 10:01:57 UTC+2, drewhk a écrit : >> >>> Hi Benoit, >>> >>> I wasn't proposing ActorProucer to loop back, instead you should >>> encapsulate the scrollId

Re: [akka-user] Sending a message after Future(s) completion

Happy hAkking! On Fri, Jun 27, 2014 at 12:22 PM, Jasper wrote: > Oh I see, it looks better indeed. Thanks. > > Le vendredi 27 juin 2014 12:15:38 UTC+2, √ a écrit : >> >> Oh, it's even better, use "recover" instead of "recoverWith". >> >> >> On Fri, Jun 27, 2014 at 12:14 PM, Jasper wrote: >> >>

Re: [akka-user] ̣̣[akka-stream] Looping or recusrion in Duct / Flow

On Fri, Jun 27, 2014 at 11:59 AM, benq wrote: > > > Le vendredi 27 juin 2014 10:01:57 UTC+2, drewhk a écrit : > >> Hi Benoit, >> >> I wasn't proposing ActorProucer to loop back, instead you should >> encapsulate the scrollId state and corresponding behacior in that >> ActorProducer -- i.e. you im

Re: [akka-user] Sending a message after Future(s) completion

Oh I see, it looks better indeed. Thanks. Le vendredi 27 juin 2014 12:15:38 UTC+2, √ a écrit : > > Oh, it's even better, use "recover" instead of "recoverWith". > > > On Fri, Jun 27, 2014 at 12:14 PM, Jasper > > wrote: > >> Missed to wrap the Nil in a Future, but it works perfect, thanks ! >> >>

Re: [akka-user] Sending a message after Future(s) completion

Oh, it's even better, use "recover" instead of "recoverWith". On Fri, Jun 27, 2014 at 12:14 PM, Jasper wrote: > Missed to wrap the Nil in a Future, but it works perfect, thanks ! > > Le vendredi 27 juin 2014 12:00:18 UTC+2, √ a écrit : >> >> WARNING: Did not try to compile this >> >> Future.seq

Re: [akka-user] Sending a message after Future(s) completion

Missed to wrap the Nil in a Future, but it works perfect, thanks ! Le vendredi 27 juin 2014 12:00:18 UTC+2, √ a écrit : > > WARNING: Did not try to compile this > > Future.sequence( > futureFiles map { _ recoverWith { case ex => log.info("Retrieval of > files failed : {}", ex.getLocalizedMessag

Re: [akka-user] ̣̣[akka-stream] Looping or recusrion in Duct / Flow

A Producer is not a Consumer On Fri, Jun 27, 2014 at 11:59 AM, benq wrote: > > > Le vendredi 27 juin 2014 10:01:57 UTC+2, drewhk a écrit : > >> Hi Benoit, >> >> I wasn't proposing ActorProucer to loop back, instead you should >> encapsulate the scrollId state and corresponding behacior in that

Re: [akka-user] Sending a message after Future(s) completion

WARNING: Did not try to compile this Future.sequence( futureFiles map { _ recoverWith { case ex => log.info("Retrieval of files failed : {}", ex.getLocalizedMessage); Nil } } ).map(lists => Detected(lists.flatten.toIndexedSeq)) pipeTo sender On Fri, Jun 27, 2014 at 11:22 AM, Jasper wrote: >

Re: [akka-user] ̣̣[akka-stream] Looping or recusrion in Duct / Flow

Le vendredi 27 juin 2014 10:01:57 UTC+2, drewhk a écrit : > > Hi Benoit, > > I wasn't proposing ActorProucer to loop back, instead you should > encapsulate the scrollId state and corresponding behacior in that > ActorProducer -- i.e. you implement your original snippet not in terms of > flow,

[akka-user] ANNOUNCE: First akka-http-core preview and updated akka-stream preview

Dear Akka and Spray community, we are very happy and excited to release the first preview of Akka HTTP’s core module based on an updated preview of Akka Streams. It is the fruit of the collaboration between the Spray and Akka teams and aims to bring you fully reactive HTTP streams. Both HTTP re

[akka-user] Sending a message after Future(s) completion

Hello, Beginner here, I'm experiencing some issues with a particular portion of my code : val paths = ListBuffer.empty[List[File]] futureFiles.foreach{ _.onComplete{ case Success(list: List[File]) => paths += list case F

Re: [akka-user] ̣̣[akka-stream] Looping or recusrion in Duct / Flow

Hi Benoit, I wasn't proposing ActorProucer to loop back, instead you should encapsulate the scrollId state and corresponding behacior in that ActorProducer -- i.e. you implement your original snippet not in terms of flow, but inside the ActorProducer. Then you can compose that stream with others.

Re: [akka-user] Re: Reactive applications with CQRS and Akka Persistence?

Hi Ashley, Op vrijdag 27 juni 2014 06:57:17 UTC+2 schreef Ashley Aitken: > > Hi Jeroen, > > On Friday, 27 June 2014 05:13:54 UTC+8, Jeroen Gordijn wrote: > > Why do you need a view that watches multiple Processors? This can already >> be achieved. You create a child View for every Processor you w