Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

Who is eating our connections? #1492

Open
yaronyg opened this issue Nov 4, 2016 · 5 comments
Open

Who is eating our connections? #1492

yaronyg opened this issue Nov 4, 2016 · 5 comments

Comments

@yaronyg
Copy link
Member

yaronyg commented Nov 4, 2016

Someone is sitting on our connections and making us run out. Who is it?

@andrew-aladev
Copy link
Contributor

andrew-aladev commented Nov 7, 2016

We need to destroy free sockets explicitly. Related to request/forever-agent#30.

@andrew-aladev
Copy link
Contributor

We've fixed forever agent and now our test can be stopped only because of jxcore segfault. I had about 300 dead sockets on Friday after 10 rounds and now I have only 2 dead sockets. Something was not closed properly. I think we can reopen this issue with lower priority.

@larryonoff
Copy link
Contributor

We've created our fork of forever-agent, see thaliproject/forever-agent.

@yaronyg
Copy link
Member Author

yaronyg commented Nov 8, 2016

@larryonoff I thought @andrew-aladev said we still have a slow leak and should keep this issue open but at a lower priority since the leak looks quite slow?

@larryonoff
Copy link
Contributor

@yarong we still have leak, but very slow. It least as we know now. So I'm reopening the issue but lower the priority.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants