Hello, I just updated from developer version 2.3.0.1 to the new version 4.2.1.4 (I am really, really risk adverse). Anyhow, I do only look up in Historical TCP/IP mode - lots and lots a day.

The error I am seeing is that it is throwing a SocketTimeoutException while reading from a socket. The exception message is: "Read timed out"

Here is the relevant code:

try
{
//write to the socket
sout.write( command );
sout.flush();

//read the response from the socket
String line = sin.readLine();

while( line != null && !line.trim().equals( "!ENDMSG!" ) )
{
if( line.length() != 0 )
{
// we do something
}
line = sin.readLine();
}
}
catch( SocketTimeoutException timeoutException )
{

}

Any ideas?

After doing a bit of research, I am not sure why this would be happening for you.

Can you give some more inforamtion about the requests? Are you able to complete any requests at all? If so, does the error occur randomly or is it always on a specific request?

Have you tried to enable logging in IQConnect to see if an error is output to the log by IQConnect?

I will definitely turn on the logging but, after re-examining the code, I have another theory that may solve it. Here is what I think is happening.

I am registering with the DTNClient and making calls. Then I think the socket is dying ('Read Time Out' and then all subsequent calls die until the socket can be re-established. If this theory is correct, is a way to listen for socket issues/statuses on the client?

For completeness, we determined that this had nothing to do with DTN, but it was a network routing issue on our end.