Re: [akka-user] Akka-stream: onComplete not called properly when mapAsync s used

issue found: http://stackoverflow.com/questions/31926637/akka-stream-oncomplete-called-before-mapasync-has-finished-to-process-data On Mon, Aug 10, 2015 at 10:29 PM, Viktor Klang wrote: > Hi Olivier, > > could you pleaseprovide us with a minimized executable reproducer? > > On Mon, Aug 10, 2015

Re: [akka-user] Warning documentation on the Http.bindAndHandle methods

Thanks for the pointer, Johannes fixed that in this commit right away (without telling anyone ;-) ). Regards, Roland On Mon, Aug 10, 2015 at 2:11 PM, Chris Baxter wrote: > The bindAndHandle methods on the Http exten

Re: [akka-user] [Akka 2.1.4] ConsistentHash router and memory issues

Hi Dima, as far as I can see the implementation is quite wasteful in creating these ConsistentActorRef wrappers (100K for every message send in your case). 2.3.12 should be much smarter in this regard … Regards, Roland On Mon, Aug 10, 2015 at 12:44 PM, gutzeit wrote: > Hey, > > I am using akk

Re: [akka-user] Re: Akka HTTP web-socket authentication session ID

Hi Guido, for server-sent events (i.e. SSE) there is this example , although it only covers the case where the stream of events is already known at the time the re

Re: [akka-user] Re: Akka Streams and OAuth 2.0

I'm confortable with Scala, but for reasons outside my control, Java was mandated for this project. We're using streams for another part of the application, in a somewhat simpler scenario. This conversation has been very helpful. The gems are these, I think: a) Treat the refresh flow as normal pro

Re: [akka-user] Re: akka-http 1.0 RC and SSL and Java

The SSLContext is responsible for handling the trust store -- you set it up and pass that into akka-http using HttpsContext.create(sslContext,...). How to set up the SSLContext is a bit confusing. There are examples in the guides for Android: https://developer.android.com/training/articles/secur

[akka-user] Persistent actor partitioning question

So imagine I am building a session tracking system. Where I am feeding the session header, events, and other things about the session and maintaining its state in a single actor. Now I am looking to add fault tolerance to that actor for when I need to either rebuild my Index for slicing and di

[akka-user] Application fails silently at http request, what could be wrong?

I have created this bot to prank my friends, and study some Akka in the process. But I am having a problem that I am unable to solve, so I was hoping someone might have a clue. The code is at https://github.com/nlw0/hackfm . What it does is to enter a page that has a simple pool, fetch current

Re: [akka-user] Using cluster aware pool routers with remote deployment

Uff, indeed :-) Gotta watch out and only keep as many ActorSystems as you really intent to have. Glad you found the solution, happy hakking! --  Cheers, Konrad 'ktoso’ Malawski Akka @ Typesafe On 10 August 2015 at 10:31:31, n...@rubell.com (n...@rubell.com) wrote: Hi, I am trying to use round-

[akka-user] Re: Using cluster aware pool routers with remote deployment

After looking into the details of the problem closer, I found the problem is not in the configuration but rather in the code itself. I've made a typo and had: def system = ActorSystem("mySystem") instead of val system = As a result the actor system was instancitated each time system was us

[akka-user] akka-streams best practice for periodically doing work

Hi, suppose I want to periodically do the following 'work': - access a database to obtain a 'lock' (only one of a bunch of scaled out services are to do the work at once) - start some 'process' that periodically touches the lock - interact with a remote resource (download a file from ftp server

Re: [akka-user] Re: Akka Streams and OAuth 2.0

Oh, jeez. Yeah, that's entirely hideous. You know there's a cure for this disease. It's called Scala. However, side effects may include crawling compiles, awkward builds, and speaking optionally in futures :-) Seriously, if I'd known you were approaching this from Java, I'd advised against usi

Re: [akka-user] Re: Coordinator in cluster sharding: No oldest node

We have improved the way roles and proxies work significantly in 2.4-M2: http://doc.akka.io/docs/akka/2.4-M2/scala/cluster-sharding.html On Mon, Aug 10, 2015 at 9:41 PM, Yifei wrote: > Thanks Patrik, > > I have the scenario shown below: > > There are 3 shard regions, A, B and C, A send messages

[akka-user] akka-streams example for accessing a database or similar?

Hi all, I am looking for an akka-streams example that shows how one would approach talking to databases (or an FTP server in my case). Besides the basic question of how to create a Source or Sink on top of a database driver (or SFTP connection for that matter) I am looking for best practices o

Re: [akka-user] Best practice for communicating with a cluster: client vs direct membership

Hi, I agree that it strongly depends on your application. But it is an aspect that one should consider when planning the architecture, that's why I mentioned it. best Carsten Am Mittwoch, 12. August 2015 10:40:20 UTC+2 schrieb Heiko Seeberger: > > Carsten, > > I don’t think your argument is v

Re: [akka-user] Best practice for communicating with a cluster: client vs direct membership

Carsten, I don’t think your argument is valid for a typical frontend/backend grouping of a cluster where you have N frontend (HTTP) nodes and M backend nodes. Assuming you use a reasonable strategy to distribute backend actors across the M backend nodes, e.g. by using a cluster aware router or

[akka-user] Re: [akka-stream] What is the best way to acknowledge completion?

Dom, Have a look at my library, `op-rabbit`. I am planning to lift out the acknowledged stream component so it can be used on it's own. On Thursday, May 28, 2015 at 9:19:18 AM UTC-6, Dom B wrote: > > Hi, > > I'm looking at the new Streams API and trying to work out if it's a best > fit for my u

[akka-user] Re: Best practice for communicating with a cluster: client vs direct membership

Hi, another aspect to consider is message volume. My experience with the cluster client is that the communication might become unstable under high load. The reason is, AFAIK, that the communication between actor systems is done via a single TCP connection and all messages go via that connection