Re: [akka-user] Re: akka kafka stream parallel processing

Many examples using lambda expression, like this Consumer.Control c = Consumer.committablePartitionedSource(consumerSettings, Subscriptions. topics("topic1")) .map(pair -> pair.second().via(business()).toMat(Sink.ignore(), Keep.both()) .run(materializer)) .mapAsyncUnordered(maxPartitions, (pair)

Re: [akka-user] Akka Flow map from X to X, the materialize

A flow is not something you can run - it's defined as "one open input, one open output". What the method fromSinkAndSource builds is like a flow made from two discrete parts. Imagine that it's input will be drained to the given sink, and it's output IS the source you gave it. If you just want to

[akka-user] HTTP - ask actor does not stop when client closes connection

The following experiment registers for termination of the internal actor used by the ask pattern. The Termination message is received when the route completes normally or times out. Closing the connection from the client has no impact on the internal actor, which survives until the timeout

Re: [akka-user] Akka Flow map from X to X, the materialize

Hi Igmar, You can do a map on the source and pass the new returned Source as the second parameter to Flow.fromSinkAndSource instead of the original source. Something like this (untested): final Source source = Source.range(1, 100).map(v -> new X()); final Sink

[akka-user] ANNOUNCE: Akka-Http 10.0.6 Security Update Released

Dear hakkers, We are proud to announce Akka Http 10.0.6, which is the sixth release of the Akka Http 10.0 series. It contains an important security fix for a vulnerability that affects all Akka HTTP applications that use the routing DSL. The vulnerability allows a remote attacker to crash an

[akka-user] ANNOUNCE: Akka HTTP 2.4.11.2 Security Patch Released

Dear hakkers, We announce the immediate availability of the second security patch for the experimental Akka HTTP that was part of the 2.4.x development series. It contains an important security fix for a vulnerability that affects all Akka HTTP applications that use the routing DSL. The

[akka-user] akka-http Client-Side HTTPS Support MITM Warning

Hi there, We're evaluating the usage of akka-http for one of our projects. I see a warning message on the top of http://doc.akka.io/docs/akka-http/10.0.0/scala/http/client-side/client-https-support.html stating the following: Warning Akka HTTP 1.0 does not completely validate certificates

Re: [akka-user] akka-http Client-Side HTTPS Support MITM Warning

Hi Ferenc, please do always read the latest docs - this is an ancient note you stumbled upon. "1.0" refers to a version released back in July 2015 (!), at which time we did not have the certificate checking implemented. By now it is, and the note is gone from the docs:

[akka-user] Re: Blocking operation and dispatcher thread

2nd option is usually the way to go and if it involves I/O operations dispatcher of thread-pool type will behave better than a fork-join. HTH, Guido. On Sunday, April 30, 2017 at 8:24:53 AM UTC+1, Thibault Meyer wrote: > > Hello, > > > what is the best way to proceed with blocking operation ?

Re: [akka-user] Akka-Java Routing Issue

I'm not sure if you can "forward" instead of "route" to a router, if not you could probably set the router sender to sender() and just reply to the sender from the processing actor, that way you won't need to correlate, it should be do-able using existing sender() reply mechanism. The trick

[akka-user] Akka Flow map from X to X, the materialize

Hi, I'm starting to learn the basics of Akka Streams, and I have this : final Source source = Source.range(1, 100); final Sink sink = Sink.foreach(v -> System.out.println(v)); final Flow flow = Flow.fromSinkAndSource(sink, source);