Community
Participate
Working Groups
In case a client is slow to read and eventually sends a RST, the SSL machinery spins, causing 100% CPU.
The spin was caused by a catch block that was eating the exception thrown (the exception was thrown due to the RST sent by the client), so Jetty was never closing the endpoint associated. Fixed by closing the endpoint and rethrowing the exception.