Hi, I am not sure I fully understand what you try to achieve. Throttle only stores one message, so there will be only one message outstanding when its upstream is closed, It might take some time to emit that, that's true, but this is what it supposed to do.
If you don't want a proper close/complete here (since that waits for any previous element to be properly passed first to the last stage) but a failure. Failures are propagated immediately, independently of any previous message being in buffers/delayed etc. But a more general question, why are you closing the receiving actor before all the elements has been passed to it? Just because the client closed the connection it does not mean that it does not want the previous messages to be delivered. As an example: 1. I am in room, and type "Bye!" 2. I close the client I expect "Bye!" to be still delivered -Endre On Fri, May 6, 2016 at 10:47 AM, Magnus Andersson < magnus.anders...@mollyware.se> wrote: > Hi > > You're right, I read the buffer as being the input buffer not the output > buffer. As for the kill switch I haven't used it myself so I'm not much > help there, I thought the underlying assumption was wrong. > > /Magnus > > tors 5 maj 2016 kl 09:56 skrev hamid <hrdav...@gmail.com>: > >> Thank you for the reply. >> >> First, I want to use backpressure strategy to put a limit on incoming >> messages which I believe that's what this line is for: >> .throttle(1, 1 seconds, 1, ThrottleMode.shaping) >> I think this line causes a backpressure on client side so I'll not >> receive no more messages than 1 per second. (Unless you tell me I'm wrong!) >> I've tried "delay(1 seconds, backpressure)" as well, which also I think >> is the same! (unless again you tell me i'm wrong!), and caused the same >> effect. >> >> Secondly, By "1000mgs and a overflow strategy ", I think you are >> referring to buffer of outgoing messages, which I've nothing to worry >> about, unless again you give a me reason to! cause i've tried and sending >> more than 1000s/buffer is not supported for backpressuring. >> >> Let me tell you what I'm experiencing here. >> When a websocket starts I'll send the actor of websocket which is this loc >> val actorAsSource = builder.materializedValue.map(actor => >> UserJoined(user_id, rooms, actor)) >> to a sink.actorref to gather them, and connect the "fromWebsocket" to it >> as well with a merge. >> val chatActorSink = Sink.actorRef[ChatEvent](chatRoomActor, >> UserLeft(user_id, rooms)) >> val mergeToChat = builder.add(Merge[ChatEvent](2)) >> actorAsSource ~> mergeToChat.in(0) >> fromWebsocket ~> mergeToChat.in(1) >> mergeToChat ~> stopper ~> chatActorSink // look at the stopper >> here! *** >> >> >> >> What happens here, is kinda surprise to me, when I kill the websocket >> client(a nodejs script) by (ctrl+c), the console(sbt running my scala app) >> prints >> [INFO] [05/04/2016 19:32:10.981] [akka-system-akka.actor.default- >> dispatcher-8] >> [akka://akka-system/user/StreamSupervisor-0/flow-14-0-actorRefSource] >> Message [io.scalac.akka.http.websockets.chat.ChatMessage] from >> Actor[akka://akka-system/user/chat-53aff88cdc302896c7000022#71135517] to >> Actor[akka://akka-system/user/StreamSupervisor-0/flow-14-0-actorRefSource#-676858346] >> was not delivered. [6] dead letters encountered. This logging can be turned >> off or adjusted with configuration settings 'akka.log-dead-letters' and >> 'akka.log-dead-letters-during-shutdown' >> What I think is happening here is this: >> Since I'm using the "throttling" to limit the incoming messages, I think >> it causes a delay also when it comes to closing stream, it wont happen >> unless throttling finishes so it will bring a unnecessary delay but the >> actor is dead and the messages it gets will be logged as a dead letter >> messages. >> >> Btw, even if my assumptions are wrong I really like to know the answer of >> "how can I use killswitch" in this matter to learn the akka-streams better. >> >> Thank you. >> >> >> On Wednesday, May 4, 2016 at 11:39:28 AM UTC+4:30, Magnus Andersson wrote: >>> >>> I don't understand how you are to detect this behavior. >>> >>> You have a throttle for 1mgs/sec and a buffer of 1000mgs and a overflow >>> strategy to drop messages. The messages will keep coming if you don't fill >>> up the buffer, up to 1000 seconds after upstream has stopped sending >>> messages. Is this what you are talking about? >>> >>> >>> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Akka User List" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/akka-user/OisR-nYVJXA/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> akka-user+unsubscr...@googlegroups.com. >> To post to this group, send email to akka-user@googlegroups.com. >> Visit this group at https://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > -- > Magnus Andersson > Mollyware AB > > +46-738-403885 > magnus.anders...@mollyware.se > www.mollyware.se > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: > http://doc.akka.io/docs/akka/current/additional/faq.html > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to akka-user+unsubscr...@googlegroups.com. > To post to this group, send email to akka-user@googlegroups.com. > Visit this group at https://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- Akka Team Typesafe - Reactive apps on the JVM Blog: letitcrash.com Twitter: @akkateam -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
