Submitter has created a scenario where mutiple threads each create a
socket with SO_TIMEOUT set. Only one binds to one ServerSocket.

It's assumed that the remaining sockets should throw a
SocketTimeoutException.
On windows, it seems like the clients stay in the socketRead0 state.

This was reproduced on windows. Unix seems to be ok. I haven't been able to
reproduce yet but am logging this bug for reference. Will attach a testcase.