Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Severe performance degradation in HTTP Server with keep alive connections #269

Closed
knopp opened this issue Aug 21, 2013 · 1 comment
Closed

Comments

@knopp
Copy link

knopp commented Aug 21, 2013

We're experiencing problem with the HTTP server. Each HTTP request with keep-alive connection blocks thread until the connection timeouts. With enough concurrent requests, the thread pool runs out of threads and all new requests are blocked until the oldest connection timeouts.

I think instead of blocking the thread, the thread should be returned to pool and select should be run on idle keep-alive connections.

Is this a known issue?

@Masuzu
Copy link

Masuzu commented Jan 23, 2017

Same issue for me there. I had to close manually the connection on the client side to avoid having too many threads in the thread pool.

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

No branches or pull requests

3 participants