Description
There's an issue with the auto+nio+ssl transport where the task that runs to read enough byets to detect the protocol can continue to run even after the timeout period. This ends up eating up cpu and the task will never stop.
This can happen if there's a repeated exception when trying to read from the protocol or when the client connects but doesn't send enough bytes.