[akka-user] Re: What's the replacement for Akka Actor Publisher and Subscriber?

I have a JS Websocket streaming into an Akka Http Server; but I want to keep in-memory the latest aggregate state in an Akka Actor. i.e. Is that just using CQRS on the datastore, so I wouldn't be connecting the Akka Actor (Query Read Response-side) directly to the Akka Http Server (Command)

[akka-user] Re: Memory Bounding Akka Streams

> > LATEST updated understanding I have then is the following; and happy for > anyone to correct my (Newbie) understanding with a link to a clear Blog > Post or GitHub repo illustrating this concept! > > I had got this information from the excellent Manning book, 'Akka In > Action'. That

Re: [akka-user] Memory Bounding Akka Streams

LATEST updated understanding I have then is the following; and if someone could PLEASE correct my (Newbie) understanding with a link to a clear Blog Post or GitHub repo illustrating the concept! 1) The Akka Stream Graph DSL API's abstraction-level hides the details of handling Backpressure

[akka-user] Message not delivered log entry, after log entry of message having been delivered?

I have one actor that sends a message to another actor. There is a message logged that the message is sent and a message logged that it was received, then later there is a message saying that the message could not be delivered. Is this normal? Essentially, I have (java): ActorRef actorB =

Re: [akka-user] Unmarshalling using javadsl

Okay. Well maybe you can help me figure out how to structure this better. I currently have a route specified that breaks down different URLs and spawns an actor whose job it is to process requests for that URL. The work of each actor typically involves a fair amount of async business logic

Re: [akka-user] Unmarshalling using javadsl

If you're a Java user I'm not quite sure how you arrived at the concept of per request actors, esp implemented like that. a) This won't work - completing must be done in a route. And ... b) use the entityAs() directive, it is documented, please check the docs. Also:

[akka-user] Unmarshalling using javadsl

Hi, I'm new to Akka Http and have been working on implementing a RESTful service using the actor-per-request model. So far I've gotten everything working but I am stuck at unmarshalling the entity in my request handler actor. While there are lots of documentation for using unmarshal directives

Re: [akka-user] Akka HTTP Stream listener stops processing databytes after a while

Thank you. that was the reason: EntityStreamSizeException: actual entity size (None) exceeded content length limit (8388608 bytes)! You can configure this by setting akka.http.[server|client].parsing.max-content-length or calling HttpEntity.withSizeLimit before materializing the dataBytes

Re: [akka-user] Akka HTTP Stream listener stops processing databytes after a while

Add a log() stage to the flow. -- Konrad `ktoso` Malawski Akka @ Lightbend On 28 September 2016 at 14:21:28, Tal Beno (tal.b...@gmail.com) wrote: I have an app which has 3 HTTP listeners like this one: val futureResponse1: Future[HttpResponse] =

[akka-user] Re: Akka Http Client - Encoding issue

Hi Andre, Thanks for your response. I will try that and see how that works. Thanks, Srinaath On Monday, September 19, 2016 at 7:43:11 AM UTC-5, André wrote: > > Hi Srinaath, > > does it work with > > "https://example.com/customers/~/profiles/dj2bQryHPCj4IVrc48xTPD > hswk%2FqNWx

[akka-user] Problem detecting Websocket failure

Hi, I have a problem detecting a failing websocket. I already got some help inside the akka issue tracker, so thanks for getting me started there even though it was the wrong place : val source = Source.actorRef[Message](bufferSize, OverflowStrategy.fail) val flow = Flow