Re: [akka-user] Reactive actor-actor communication

Hi Adam, your initial point of creating a growing (and maybe thundering) herd of retries is a good one and it would be better if we would limit the number of messages to be resent. Could you open a ticket for that? Thanks, Roland Sent from my iPhone > On Nov 18, 2014, at 04:08, Adam Warski

Re: [akka-user] Testing per-request child creation

This does rather beg the question of what the integration boundary is, and also if the use case in question ends with an ack back to the initiating actor, how would one test for that message (or its effect), given that it's a TestActorRef rather than a TestProbe. On Tue, Nov 18, 2014 at 3:08 PM,

Re: [akka-user] Testing per-request child creation

Thanks for the input. I guess I can register a testprobe.ref as a subscriber to the event bus. I will still need to control the creation of the per-request child so that I can inject a mock storage interface that acks with success so that the posting to the event bus occurs. On Tue, Nov 18, 2014 a

Re: [akka-user] Testing per-request child creation

You can test that the parent passed the correct set of results to the child actor by observing the results of the child actors processing. Usually it becomes tricky to apply Unit Testing to Actors, think Integration testing instead (but at a microlevel). On Tue, Nov 18, 2014 at 11:43 PM, Richard

Re: [akka-user] Testing per-request child creation

The message A in the parent actor is computing a set of results. The per-request child will be saving some state from those results, and if successful, posting a domain event containing the results to an event bus and also acking back to the parent. To begin with, I just wish to test that the pare

Re: [akka-user] Testing per-request child creation

Hi Richard, what effects are you trying to test? On Tue, Nov 18, 2014 at 11:17 PM, Richard Rodseth wrote: > I have a parent actor which, on receipt of a certain message A, spawns a > child actor, and sends it a "Run" message with no parameters. The child > actor has constructor parameters deriv

[akka-user] Testing per-request child creation

I have a parent actor which, on receipt of a certain message A, spawns a child actor, and sends it a "Run" message with no parameters. The child actor has constructor parameters derived from the contents of message A. What's the best way to test this? I don't think I can apply techniques like chil

Re: [akka-user] Re: Akka persistence: Optimistic Locking

Thanks for your feedback Am Montag, 17. November 2014 13:14:13 UTC+1 schrieb Konrad Malawski: > > Hi Martin, > This is all journal dependent - it's up to the journal implementation to > decide how to deal with this, > where as the default answer should be that "don't do this". Otherwise > you'd

Re: [akka-user] ActorPath vs ActorSelection in AtLeastOnceDelivery

Hmm, yes I see your point and that it could be a perfectly fine use case. Would you mind opening a ticket so we can have a look at it once we have some spare cycles? Thanks in advance! -- cheers, Konrad `ktoso` Malawski -- >> Read the docs: htt

Re: [akka-user] ActorPath vs ActorSelection in AtLeastOnceDelivery

In my particular case, I have an ActorSelection that I'm trying to send to. If I could feed that to `deliver` directly, the code would be quite simple. Right now I'm getting an ActorPath from the selection by doing `ActorPath.fromString(actorSelection.toSerializationFormat)`, although this fee

Re: [akka-user] Aeron as Akka's transport layer ?

It would be really nice to get an idea of the timeline.  "When it’s done” ;-) I’m sorry, but we’re not able to commit to these features nor dates for them as of now. It’s something we look into and is very tempting to implement. For now though we’re all focused on getting streams out the

Re: [akka-user] Aeron as Akka's transport layer ?

Konrad, That's very reassuring to hear. If the claims made by Aeron are true it can be a game changer. Imagine an super faster transport layer, combined with an efficient serialization format can make Akka even more compelling :-) It would be really nice to get an idea of the timeline. Also

[akka-user] Re: [akka-streams] Dynamically add route output port

Some messages belong in more than one sub-stream - how would I accomplish that using groupBy? On Sunday, November 16, 2014 1:42:48 AM UTC+1, Oscar Broman wrote: > > Hello! > > I've been messing around with akka-streams lately and ran into some > problems. I'm not sure where to go from this point

Re: [akka-user] Router Like Behavior with Streams

That's what we're doing in the interim, just wanted to make sure we weren't missing something. Thanks for the work on streams! On Tue, Nov 18, 2014 at 8:50 AM, Konrad Malawski wrote: > For now you'll have to push it to an Actor{Subscriber / Publisher} > boundary and take it from there into remot

[akka-user] Recording of Dr. Roland Kuhn's webinar of Akka Roadmap Update?

Hello, Unfortunately, I was not able to attend yesterday's Webinar. Was the event recorded? If so, can someone post the link please? Thanks, Chanan -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/

Re: [akka-user] Router Like Behavior with Streams

For now you'll have to push it to an Actor{Subscriber / Publisher} boundary and take it from there into remoting. We're also very much looking forward to streams in clusters, but for now the local ones are loads of work and fun already :-) On Mon, Nov 17, 2014 at 4:17 PM, Danny Browning < danny.br

Re: [akka-user] [akka-streams] Dynamically add route output port

Sounds to me like you could get away with using groupBy - where you assemble the group key based on your criteria. Elements with the same criteria end up in the same "sub-stream". Ha

Re: [akka-user] Re: [akka-streams] ActorPublisher-based Source

No, the actor system is alive. Additionally, i have repeated that code many times with the same result: for (i <- 1 to 10) { Source(list).mapConcat(x => x).runWith(ForeachSink(println)) } вторник, 18 ноября 2014 г., 16:29:08 UTC+4 пользователь Patrik Nordwall написал: > > Do you shutdown t

Re: [akka-user] UnboundedControlAwareMailbox and ControlMessage

Opps, Didn't noticed it was a snapshot of 2.4. Thanks, On Tuesday, November 18, 2014 2:29:31 PM UTC+2, Konrad Malawski wrote: > > Hey there, > These are not the docs you're looking for :-) > > Your docs link: http://doc.akka.io/docs/akka/*snapshot* > /java/mailboxes.html#ControlAwareMailbox >

Re: [akka-user] routing and load balancing with AKKA instead of regular NLB

Hi Konrad, Thanks. I know all of Akka's concept (reading the documentation and articles) and I understand it is a little funny Q. On top of that - of course we will continue to POC. As I mentioned we are confident with Akka and using it's advantages BUT since we are new to Akka, we had some debat

[akka-user] Akka allocates new socket for each unsuccessful connection attempt to a quarantined system.

Hello, I'm using Akka 2.3.4 running on Java 1.7.0_72 in Ubuntu 14.04 I'm reproducibly falling into the situation when a remote system is quarantined and for each unsucessful attempt to connect to that remote system a new socket is allocated but never disposed. Eventually this leads to reaching

Re: [akka-user] UnboundedControlAwareMailbox and ControlMessage

Hey there, These are not the docs you're looking for :-) Your docs link: http://doc.akka.io/docs/akka/*snapshot* /java/mailboxes.html#ControlAwareMailbox The versions you're checking: 2.3.2, *2.3.7* The docs link you

Re: [akka-user] Re: [akka-streams] ActorPublisher-based Source

Do you shutdown the actor system prematurely? /Patrik On Tue, Nov 18, 2014 at 1:24 PM, Boris Lopukhov <89bo...@gmail.com> wrote: > I have isolated the problem, it seems that ActorPublisher is not the cause: > > val list = List.range(1, 21).grouped(5).toList > Source(list).mapConcat(x => x).ru

[akka-user] Re: [akka-streams] ActorPublisher-based Source

I have isolated the problem, it seems that ActorPublisher is not the cause: val list = List.range(1, 21).grouped(5).toList Source(list).mapConcat(x => x).runWith(ForeachSink(println)) expectation: 1..20 reality: 1..16 понедельник, 17 ноября 2014 г., 19:46:58 UTC+4 пользователь Boris Lop

Re: [akka-user] Reactive actor-actor communication

Hey, It would be more complicated to "replace" AtLeastOnceDelivery with your > demand-driven proposal - the entire point of ALOD is that it fights back > the fact that messages can get lost and nodes can go down. > Effectively what you're proposing is to switch from "re-sending until I > get co

Re: [akka-user] IllegalStateException in akka.dispatch.BatchingExecutor$Batch.run

Thanks a lot for creating the issue Maxim! Let us know if you'd be able to find any more details that would help us find the root cause of the issue. Thanks in advance -- Cheers, Konrad 'ktoso' Malawski hAkker @ Typesafe -- >> Read the docs: http://akka.io/docs/ >> Ch

Re: [akka-user] IllegalStateException in akka.dispatch.BatchingExecutor$Batch.run

Hello! I created new issue https://github.com/akka/akka/issues/16327. I'm going to reproduce this problem later with logging settings that was suggested by Viktor and also update Akka to 2.3.7. Maxim понедельник, 17 ноября 2014 г., 20:18:07 UTC+3 пользователь Konrad Malawski написал: > > Than

Re: [akka-user] Reactive actor-actor communication

Hi Adam, It would be more complicated to "replace" AtLeastOnceDelivery with your demand-driven proposal - the entire point of ALOD is that it fights back the fact that messages can get lost and nodes can go down. Effectively what you're proposing is to switch from "re-sending until I get confirmati

Re: [akka-user] routing and load balancing with AKKA instead of regular NLB

Hi Tzivka, The questions you're asking seem very general and maybe not on-spot as Akka is not just a router/load-balancer thingy. It's much more - a way to build ditributed peer to peer communicating applications. We do have routers and other tools like this, but it seems to me that you're trying t

Re: [akka-user] Aeron as Akka's transport layer ?

Definitely, it would be a great transport layer! No worries, we are looking at it very closely – now the only remaining question is timelines... ;-) -- Konrad `ktoso` Malawski Akka Team Typesafe - The software stack for applications that scale Blog: letitcrash.com Twitter: @akkateam --

Re: [akka-user] Re: How to Monitor akka, improving performance

Hi Gaurav, the multiple threads show up because Akka is using thread pools (multiple threads) for running Actors - which is why you’ll see systemName-dispatcher-...-N threads. It’s tough to say what exactly might be causing the threads to wait without more details on the interactions - are you sur

Re: [akka-user] ActorPath vs ActorSelection in AtLeastOnceDelivery

Hi Ryan, Thanks for the feedback! API wise I do feel it’s a bit more usable by asking for a ActorPath instead of a selection, since selection is when you “look for someone”, and you’d have to system.actorSelection(sender().path) for example. By taking an ActorPath you’re able to simply write: deli

Re: [akka-user] Accessing Future's onComplete Internal variables

Why not call the method from within the map function? Instead of trying to get the result out of the Future, you can move more processing into the Future. On Mon Nov 17 2014 at 12:51:34 PM Syd Gillani wrote: > Alright, but I would like to send the result to an API ( a method in an > external cla

[akka-user] UnboundedControlAwareMailbox and ControlMessage

Hi, I'm trying to use the UnboundedControlAwareMailbox mailbox from http://doc.akka.io/docs/akka/snapshot/java/mailboxes.html#ControlAwareMailbox example to send ControlMessage some ators. I can't seem to find akka.dispatch.ControlMessage class under any jar in Akka 2.3.2 or 2.3.7 Am I'