title: If I got java.net.SocketTimeoutException: Read timed out, Can I figure out whether it is server problem or connectivity problem?
body: <p>While I was using SoapUI to connect to a WCF service over the internet using HTTP (basicHttpBinding), I got java.net.SocketTimeoutException: Read timed out</p>
  
  <p>This exception means that SaopUI failed to read the whole message within a time window. Is there a way to determine whether it was a connectivity problem or the server did not respond at all?</p>
  
  <p>Maybe if the client and\or the server sent some packets to each other to check the connection or something like this, I'd now where is the problem.  I believe that some protocols do this but I'm not sure whether basicHttpBinding do this. </p>
  
  <p>I actually don't have any problem anymore, I simply increased the sendTimeout in the client configuration and everything become fine.  However, I am asking whether there is a way to distinguish between connectivity problems and server problems to be able to troubleshoot similar problems.</p>