This problem still persists in 2.4.7, the fix from SERVER-10261 was not solve the entire issue.

It's possible to generate SSL handshake errors with a trivial Java program: https://gist.github.com/anonymous/a2c4a8ac8f9e38e22edf. This program loops indefinitely, opening a new SSL socket on each iteration and sending a single write (which initiates the handshake).

It eventually generates this exception: http://cl.ly/image/0A2a0j0L0S1i. Note that the alert descriptions are not consistent, suggesting some sort of corruption.

The number of iterations before an error is not consistent, and it doesn't occur if SSL debugging is enabled in the client.

See linked ticket SERVER-10261