"*Anti-virus warning* - 1 attachment contains a virus or blocked file.
Downloading this attachment is disabled. Learn more
<https://support.google.com/mail/answer/6590?hl=en>"

On Thu, Nov 20, 2014 at 12:32 PM, Sergii Vozniuk <ser...@vozniuk.com> wrote:

> Hi Konrad,
>
> Probably I didn't provide some important information:
>
> 1. In current implementation we don't stop and restart (or create new)
> actor systems after failures. Their number is unchanged from the start of
> the application. So I have no explanation why new sockets are allocated.
> 2. I have read every post on the forum about quarantines and posts related
> to "too many open file problem" and I'm sure our system doesn't fall into
> one of scenarios that have been discussed here or on stackoverflow.
>
> You can find attached a minimal example project where I can reproduce the
> problem every time (10 times out of 10)
>
> The application has
>
>    - a client that connects to a server and tries to reconnect to it
>    whenever the connection is lost
>    - a server that does nothing except accepting client connections
>    - a starter class that starts up client and server actor systems
>
> To reproduce the problem
>
>    1. Execute from project directory ./gradlew run
>    2. Wait until client is connected
>    3. Execute sudo iptables -A INPUT -p tcp --destination-port 2552 -j
>    DROP to drop all server connections
>    4. Wait until the client detects problems and tries reconnecting
>    5. Let it run for a minute
>    6. Execute sudo iptables -D INPUT -p tcp --destination-port 2552 -j
>    DROP to enable server connections
>    7. Notice quarantined state being logged
>    8. Run peridically sudo netstat -tulpna | grep 2552 and observe that
>    the number of opened sockets grows
>    9. After some time has passed (12 hours in my case) the JVM crashes
>    due to Too many open files.
>
> Tell me if you need any additional info.
>
> Regards,
> Sergii
>
>
> Четвер, 20 листопада 2014 р. 11:19:58 UTC+1 користувач Akka Team написав:
>
>> Hi Sergii,
>> This sounds like a potential bug.
>> I tried to trace this back to something obvious in the code but didn't
>> find anything yet.
>>
>> Would you mind creating an issue <https://github.com/akka/akka/issues>
>> for this and we'll have a deeper look into this then?
>>
>> --
>> Konrad,
>> Akka Team
>> Typesafe - The software stack for applications that scale
>> 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 http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Cheers,
√

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

Reply via email to