Re: [akka-user] akka dispatcher "memorize" the last round connections?

Hi Liang, It's most probably known problems with early releases of 2.3 like Patrik mentioned. There's no cache-files involved, all runtime stuff only – I'd highly recommend upgrading to the latest Akka version (or higher than 2.3.4 at least). On Sun, Sep 14, 2014 at 2:35 AM, Liang Gong wrote: >

Re: [akka-user] akka dispatcher "memorize" the last round connections?

There are some ramification for me to upgrade the akka version. Are there any work around(like delete some cache files etc) , so I can move forward? On Saturday, September 13, 2014 5:50:41 AM UTC-4, Patrik Nordwall wrote: > > > > On Fri, Sep 12, 2014 at 6:31 PM, Liang Gong > wrote: > >> Hi, >>

Re: [akka-user] Does FlowGraphBuilder need more addEdge methods?

Hi Patrik, my example here is a simplification of the particular example I'm working with. Here's an example that (hopefully?) better displays the particular issue I was actually looking at: val clientIn = SubscriberSource[A] val clientOut = PublisherSink[B] val workerIn = Subscriber

Re: [akka-user] Does FlowGraphBuilder need more addEdge methods?

Hi Carl, For simple flows, one input source and one output sink, you don't need to use FlowGraph. val in = SubscriberSource[String] val out = PublisherSink[String] val materializedFlow = FlowFrom(in).map(_.toUpperCase).withSInk(out).run() FlowGraph is intended to be used for fan-in and fan-out o

[akka-user] Does FlowGraphBuilder need more addEdge methods?

I'm playing around with 0.7 of Akka Streams and Http. The following code fails to compile: val in = SubscriberSource[String] val out = PublisherSink[String] val flow = FlowGraph { implicit b => in ~> FlowFrom[String] ~> out } However, we can fix this issue by adding in a redundant

Re: [akka-user] Akka Actors In Scala Vs Akka Actors In Java:Event Sourcing

Konrad, Thanks again. Will keep this in mind. >From benchmarking, did you mean, micro benchmarking using caliper or jmh? Or benchmarking runtime performance of overall poc code? If yes, then same poc has to be implemented separately in both scala and java, followed by performance tests on eac

Re: [akka-user] Akka Actors In Scala Vs Akka Actors In Java:Event Sourcing

Language choice should have marginal (collection conversions will happen for example) has marginal impact on performance here. If you really care you should benchmark things :-) -- Cheers, Konrad 'ktoso' Malawski hAkker @ Typesafe -- >> Read the docs: http:/

Re: [akka-user] Akka Actors In Scala Vs Akka Actors In Java:Event Sourcing

Konrad, Thanks a lot again for your brief insights :) We are in poc stage this will help us in deciding next steps. There is always a confusion scala or java? You read tons of Articles, but will end up with mixed responses. I personally like scala for the reasons you mentioned. We want to work

Re: [akka-user] need help in concurrent execution of workers

Actors are asynchronous by default. If you are sending messages over router it will send those messages to workers. As soon as the worker gets a message they will start executing their behaviour in an asynchronous and concurrent manner. if you want to send one message to all the workers then you c

[akka-user] need help in concurrent execution of workers

Hi All, I am new to akka. I am doing a project where I need to concurrently execute 20 workers.. Inside each worker there is while(true) loop which will keep executing till it gets a result . Using break to exit. and using context.stop(self) to shutdown that actor. which function to use to so

Re: [akka-user] Akka Actors In Scala Vs Akka Actors In Java:Event Sourcing

Hi Prakhyat, "It depends". We provide APIs for everything in both Java and Scala. Is it better to create actor system or actors in scala or java? > There is no "better" as it depends on your team, their skills and willingness to learn. I do think it's worth to get over the initial learning curve

[akka-user] Per-request actor trait

I asked about this on spray-user, but thought I'd try here since this list rocks and it relates to Akka and an Activator template. I'm wondering how one would make this: https://github.com/NET-A-PORTER/spray-actor-per-request/blob/master/src/main/scala/com/netaporter/routing/PerRequest.scala mor

[akka-user] Re: event sourcing: building external service based on generated events

Thanks for your reply Sean. I have read about the proposed changes of the query side in akka persistence and I think you are right regarding the use of views in this case. I'm going to have go at using a separate read store to keep track of the events processed as you suggested. Rune On Frid

Re: [akka-user] Using Scheduler vs deadline to mimic some backend: scheduler is slow(er)

Hi Alex! Let me dig into the difference between a Scheduler and a Deadline right away: def quit(m: SimpleMsg) = { // ... val deadLine = delay milliseconds fromNow*while (deadLine.hasTimeLeft()) { // A.K.A. *"hog the thread" :-) // do some work... } val stopActor = cont

Re: [akka-user] LevelDB dependency

This may be a good idea and is worth discussing when we move towards 2.4. It's worth opening an issue about this so we at least discuss it during planing of the next persistence sprint, would you mind doing that? Thanks! On Fri, Sep 12, 2014 at 12:45 PM, ahjohannessen wrote: > Hi, > > Would it n

Re: [akka-user] Rest api architecture design questions with clustering

Hello Ignacio! I'll try to address your questions, but some seem to need deeper architecture review etc, that is something we could do but probably as an commercial offering - if that's something you're interested please contact me / sales directly (made quite a few people very happy this way :-)).

Re: [akka-user] Re: Reusing ActorSystem / Actor in the web, generating unique names.

Hi Prakash, you will have to share (as in "pass around") the ActorSystem in one way or another. While a global variable with it is not the best idea for testing, it does solve the problem, agreed. Instead though (which does not break testing as much, and allows parallel tests), simply pass around

Re: [akka-user] akka dispatcher "memorize" the last round connections?

On Fri, Sep 12, 2014 at 6:31 PM, Liang Gong wrote: > Hi, > > In my system, a node keep complained "] Association with remote system > [] has failed, address is now gated for [5000] ms. Reason is: []], > however the node "" never being started this "round". The whole cluster > has bee

[akka-user] Re: Reusing ActorSystem / Actor in the web, generating unique names.

Hello All, It's Done. Thank you so much for your support & to understand my problem very easily with prompt solution. On Monday, June 11, 2012 5:58:27 AM UTC+5:30, dimgel wrote: > > Hi all, > > Since actors are stateful, I have to create an actor tree for each HTTP > request I handle, right? >