Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Fix incorrect reading of somaxconn for tcp backlog on linux #2430
Dropwizard drops connections during a burst of short lived connections, as the accept queue is set to (most commonly) 1 or 2 due to
Test passed and dropwizard should be more burst resistant. Closes #2429
Dropwizard users currently afflicted by this bug, can override this default behavior by specifying an
Jul 12, 2018
Just a note. You say that affected users can override it in settings. However, the system limit still applies.
To actually change the limit on linux, the user needs to run:
Typically added to
I suspect there is still another bug in Jetty in how it handles the sockets with refused connections. Setting higher accept queue will make it close to impossible to hit in real world scenarios though.
When we hit this issue, we see connection timeouts on the client side after 60 seconds. If it was just the accept queue full, the client would get the rejection and fail the connection right away. But it does not - instead, it keeps waiting. I think what is happening is described here: https://blog.cloudflare.com/this-is-strictly-a-violation-of-the-tcp-specification/