By HTTP (websocket) server I mean akka-http. On Sunday, June 7, 2015 at 9:17:36 AM UTC+3, Andrey Kuznetsov wrote: > > My application also has an HTTP (websocket) server on another port, it's > behind Elastic Load Balancer too, and it doesn't suffer from such problem - > there is no CLOSE_WAIT connections to it. > > On Sunday, June 7, 2015 at 7:17:44 AM UTC+3, Andrey Kuznetsov wrote: >> >> Just found this issue: https://github.com/akka/akka/issues/17122 >> So, it's akka-io problem and there is no currently any workaround when >> using akka-streams, am i right? >> >> On Sunday, June 7, 2015 at 7:03:01 AM UTC+3, Andrey Kuznetsov wrote: >>> >>> I am using akka-streams for handling incoming TCP connections. After >>> putting application behind AWS Elastic Load Balancer, it started to fall >>> into "too many open files" problem because of lots of connections in >>> CLOSE_WAIT state. Is there an ability to close such connection on a server >>> side? >>> >>
-- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
