auth and session makes context.stop(self) inside Cancel handler of their
receive's. And they see it if client closes connection (at least if it
is being closed by Connection reset by peer). I tried to send PoisonPill
to auth and session actors from Sink.onComplete and still observed
CLOSE_WAIT connections.
--
 
Andrey Kuznetsov
 
 
On Sun, Jun 7, 2015, at 08:07 AM, Endre Varga wrote:
> Hi Andrey,
>  
> When do the auth and session sources finish? Do you see the onComplete log 
> message from broadcast? Since the connections you see are in CLOSE_WAIT, that 
> means that your server already received a close from the client, but it has 
> not yet closed its own side (half-closed). I suspect that since you have more 
> than one input wired into your merge node, if the inbound mtproto flow 
> closes, the merge itself continues if the other two inputs of it are not 
> completing and therefore keeping the connection open.
>  
> -Endre
> _
>  
> On Sun, Jun 7, 2015 at 4:44 PM, Andrey Kuznetsov <[email protected]> wrote:
>> and mapResponse is a PushStage:
>>  
>> 
>> *def***mapResponse(system:ActorSystem)=*new*PushStage[MTProto,ByteString]{
>> *private*[*this*]*var*packageIndex:Int=-1
>> 
>> *overridedef*onPush(elem:MTProto,ctx:Context[ByteString])={
>>     packageIndex +=1
>> *val *pkg =TransportPackage(packageIndex,elem)
>> 
>> *val *resBits =TransportPackageCodec.encode(pkg).require
>> *val *res =ByteString(resBits.toByteBuffer)
>> 
>>     elem *match *{
>> *case*_:Drop⇒
>>         ctx.pushAndFinish(res)
>> *case*_ ⇒
>>         ctx.push(res)
>> }
>> }
>> 
>>  
>>  
>>  
>> 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.
>  
> 


> -- 
> >>>>>>>>>>      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/MC1J4q9lZYw/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
 

-- 
>>>>>>>>>>      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.

Reply via email to