I realized recently that if I add a completionTimeout to a Flow setup to make http requests through a host connection pool that I can wedge the pool when enough (4 for the default config) of these timeouts happen. I believe this is because the entity associated with the eventual response is not consumed or cancelled. What's the proper way to handle this use case when wanting to add a timeout oriented combinator to the processing Flow that won't cause the pool to wedge. Also, this may only happen when the response is chunked but I have to confirm that still.
-- >>>>>>>>>> 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.
