[akka-user] Re: TCP Handshaking custom stage drives me crazy

Thanks for the help, yes that did the trick to add one more pull for sslIn. The reason bytesIn is empty is because I really dont need a bidishape. I need this logic encapsulated in something with one input and two outputs because after this handshaking is done there is no need to send any more

Re: [akka-user] ActorPublisher GraphStage alternative?

I made some progress figuring out how to use getStageActor (not getStageActorRef - the docs have an error) - the stage’s preStart() registers the stage’s actorRef with an outside actor. Messages forwarded to that actorRef (via the outside actor) will get sent to a callback function inside the

[akka-user] Akka Messages Duplicated

I have an application that uses remote addressing exclusively. The application is under development on one local machine; one actor system spanning several JVM. When I send a message the message always arrives at its intended recipient actor and is processed. Program output verifies that the

Re: [akka-user] akka-http client: How to ensure response entity is read

Hi Roland, I realized that although I jumped into this thread, the thing I'm really interested in is not exactly consuming the timed out requests, it can be done at one time in the future. The problem is how to cancel an already started request after a timeout. I put together an example

Re: [akka-user] Remoting - no reconnect possible - name or service not known

Well, I was hoping you wouldn't respond with that. :/ I read that Akka remoting is a peer2peer framework. Nevertheless we use it partly as client-server. Probably also because the requirements were not absolutely clear in the beginning of software design. Also that doesn't explain what exactly

Re: [akka-user] Remoting - no reconnect possible - name or service not known

http://doc.akka.io/docs/akka/current/scala/general/remoting.html#peer-to-peer-vs-client-server Sorry for short answer /Patrik fre 2 juni 2017 kl. 09:35 skrev Manfred Bergmann : > Hello. > > I need some advice. > > The following situation (Akka 2.5.2): > > I have an

[akka-user] Re: Processor actor terminated abruptly on HTTPs connections (akka 2.4.12, akka-http 2.4.11)

Is there anything new about this issue. I just came across and a bit disappointed. On Tuesday, 8 November 2016 18:07:58 UTC+1, Sami Dalouche wrote: > > Also, it looks like that avoiding the use of a connection pool doesn't > trigger the issue. The following code works fine, without any error >

[akka-user] Re: TCP Handshaking custom stage drives me crazy

I spotted a mistake in the second snippet from my previous post. What I meant is the following (sorry for another post but cannot find "edit" option here): if (subscriptionValid(event)) { state = Subscribed logger.info(state.toString) if (isAvailable(bytesOut)) { pull(sslIn) } }

[akka-user] Re: TCP Handshaking custom stage drives me crazy

Hey Larsson - based on debug messages when running live I would guess that you miss `pull(sslIn)` somewhere. I have a hypothesis for what's going on. Let's take a look at: ``` setHandler(bytesOut, new OutHandler { override def onPull() = state match { case Connecting => case

[akka-user] Remoting - no reconnect possible - name or service not known

Hello. I need some advice. The following situation (Akka 2.5.2): I have an ActorSystem on one host (host0) and another ActorSystem on another host (host1). host0 is assumed to always be online and available. host0 does not know the ip address or hostname of host1 (DNS). host0 cannot make

[akka-user] Distributed Publish Subscribe in custom GraphStage

Hi all, Is there any way to combine custom GraphStage with Distributed Publish Subscribe ? I'm refactoring a ActorPublisher into a GraphStage. Thanks a lot -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

[akka-user] beginner question on akka streams flow design.

Hi , I have the following use case that I want to model using akka streams and I am new to akka streams so would like to know how/what is the best way to model it. I have a kafka consumer which reads from one topic massages the message and sends it to a RESTful external service. This