Referencing this ticket <https://github.com/akka/akka/issues/17816>, I can see that the idle connection/timeout handling is not yet in place when using pooled connections. I added a comment around the behavior of non-pooled outbound connections with timeouts hoping to get a response but nothing so far so I'm adding here in hopes of getting some clarification. If I use a non-pooled connection and use a takeWithin on the Flow to handle a timeout, and it does hit that timeout condition, failing the Flow, will the underlying single connection be closed immediately or will it stay open until a response is received from the remote server even though control does return to the code using the connection? From the debug logging it does not look like it closed the connection until a response is received. This seems to run counter to what @sirthias says about using the low level Http().outboundConnection API. How can I get this to work as expected, where my takeWithin timeout handling will close the underlying connection immediately after hitting the timeout condition?
-- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
