Failed ping on startup can leave socket dirty

Ping on startup in TransportObjectFactory.makeObject does not check the return value of ping operation, neither the tcpTransport.isValid().
Therefore, if a HotRodClientException is thrown when the response header is read from socket, the socket is left in a dirty state.
In our case this resulted in reading response to previous request (the request was written but the response was not read due to some timeout and then, when another request was executed it read the response to the first request). This caused ISPN004004: Invalid message id. Expected 2930 and received 212