JMX client doesn't fully consume heartbeat input stream, leaving sockets in CLOSE_WAIT state

[idlewis]

The Liberty JMX client starts a background thread to act as a heartbeat, and to poll the server for notifications. The client currently assumes that the heartbeat end point returns no data, when in fact it returns the class name of the JMX server class as a string.
As the input stream containing this data is not read, and the stream is not closed, the underlying socket has to wait for the JVM to eventually perform cleanup. In the meantime, the socket can be left in close wait state.

RESTMBeanServerConnection should fully consume its input streams here:

open-liberty/dev/com.ibm.ws.jmx.connector.client.rest/src/com/ibm/ws/jmx/connector/client/rest/internal/RESTMBeanServerConnection.java

Line 2379 in 74401c4

//no-op for failover polling, just break into the sleep segment