[akka-user] Akka-Stream not truncating and failing

Hello there, I am new to Akka-Stream and working on a use case where I need to parse log files. These log files have lines separated by new line. I was looked at GroupLogFile.scala

Re: [akka-user] How do I attach multiple subscribers to a stream using fanoutPublisher, actorSubscriber and FlowGraph.partial?

Here is a sketch: val dataStream: Future[Source[ByteString]] = Http().singleRequest(...).map(_.entity.dataBytes) val parseData: Flow[ByteString, DomainEvent] = ... val parsedDataStream: Future[Source[DomainEvent]] = dataStream.map(_.map(parseData)) val broadcastSink: SinkShape[DomainEvent] =

Re: [akka-user] How do I attach multiple subscribers to a stream using fanoutPublisher, actorSubscriber and FlowGraph.partial?

Hi Johannes, Thank you for your response. Can you show me what do you mean by "put the broadcast behind the entity.dataByes'? Please pardon me if this is obvious as I'm just learning. I'm using Source.single(httpRequest), not fanoutPub. The example you pointed me to use fanout, which I intend

Re: [akka-user] How do I attach multiple subscribers to a stream using fanoutPublisher, actorSubscriber and FlowGraph.partial?

Hi Abhijit, from a quick glance to your code it seems that you are broadcasting an HttpResponse and then access its `entity.dataBytes` in several branches. This is not supported. You need to put the broadcast behind the `entity.dataBytes` and not behind the stream of responses. We prepared a

[akka-user] Reliable http request-response communication

Hi, I want to share with you my little project: https://github.com/arkadius/reliable-http-client. It's a http client that passes communication via AMQP queues to akka http super pool. This solution connected with ReliableFSM gives ability that you'll never loose your response from http

[akka-user] A simple Akka JMM question

Hi, please see the code at http://pastebin.com/L0WiXTJU Does Akka garantee that changes to the ArrayList "theList" will always been seen by ExampleActor? Or asked differently does the rule from http://doc.akka.io/docs/akka/2.4.0/general/jmm.html *"The actor

Re: [akka-user] A simple Akka JMM question

Hi John, yes it will work, but keep in mind that it is *highly* discouraged to send mutable messages not only because it won't work across JVMs but also because nothing prevents you for accidental aliasing it. On Tue, Oct 6, 2015 at 9:46 AM, wrote: > Hi, > please see the

Re: [akka-user] A simple Akka JMM question

Hi, You can use the immutable builder pattern to get the same effect you're after. As for the memory visibility, The "why" is because it's very useful (and needed even for immutable data, if not properly constructed). The "how" is we use memory fences to assure that the CPU is not allowed to

[akka-user] Akka streams materialization type

Hi, I've been keeping an eye on the development of akka streams, and I was just taking a second look at it now. There is one thing that I can't seem to get my head around, which is the explicit types associated with materialization. Compared to the earlier beta versions, it feels to me that

Re: [akka-user] ANNOUNCE: Akka 2.4.0 Released

Hi again! Its not a big deal but I recognized that in contrast to akka 2.3.14 ( http://doc.akka.io/docs/akka/2.3.14/contrib/cluster-sharding.html#Configuration ,http://doc.akka.io/docs/akka/2.4-M1/scala/cluster-sharding.html)

[akka-user] Delimited framer with timeout?

So I've been trying to get into akka streams and to be honest grokking the whole thing and putting it all together has proven to be difficult so far. I understand the documentation is still a work in progress however. One thing I am trying to figure out is how to handle timeout scenarios.