ADDITIONAL SYSTEM INFORMATION :
Windows 10
openjdk version "13-ea" 2019-09-17
OpenJDK Runtime Environment (build 13-ea+31)
OpenJDK 64-Bit Server VM (build 13-ea+31, mixed mode, sharing)

A DESCRIPTION OF THE PROBLEM :
When passing a non-zero value to java.net.Socket.setSoTimeout and then back again causes high CPU load on the thread which is attempting to read from the socket. According to the API docs, a timeout of zero means infinite. From the application perspective, the read is blocking exactly as it should, but the socket implementation appears to be in an infinite polling loop of some kind without waiting. When data becomes available, the read returns as expected.

REGRESSION : Last worked in version 12.0.2

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Connect a socket, and set the timeout to a legal non-zero value. The server side writes one byte. The client then reads the byte from the socket, and then sets the timeout to zero, which means infinite. A subsequent read by the client blocks indefinitely (as expected), but the CPU load isn't zero.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Expect to see no CPU activity on the thread while waiting to read. This is the observed behavior when running the test using JDK 12.
ACTUAL -
The CPU load on the thread (and Java process) isn't zero when blocked.

---------- BEGIN SOURCE ----------
import java.net.*;

public class Test {
    public static void main(String[] args) throws Exception {
        ServerSocket ss = new ServerSocket(0);

        new Thread(() -> {
            try {
                Socket s = ss.accept();
                s.getOutputStream().write(1);
            } catch (Exception e) {
            }
        }).start();

        Socket s = new Socket("localhost", ss.getLocalPort());
        System.out.println(s);

        s.setSoTimeout(9999999);
        s.getInputStream().read();
        s.setSoTimeout(0); // should reset to infinite timeout
        while (true) {
            s.getInputStream().read();
        }
    }
}
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
Set the timeout to a very large non zero value, which is effectively infinite.

FREQUENCY : always