[DataSpider Servista] An error occurred upon exec

java.net.SocketTimeoutException: Read timed out is an error that outputs when there is no response from a connection destination even after it passes the timeout value set in the global resource.

■From the Past Cases

The following were reported in the past as a problem where there was no response from a connection destination.

Timeout setting problem

The timeout setting value set in the global resource was too small; as a result, it timed out before the response from a connection destination.
The file transfer to the server took a long time in which it exceeded the timeout setting value

The problem of connection destination or network environment

There was a problem at a connection destination and it was impossible to send a response
A port was blocked by a firewall in which it was not possible to receive a response from a connection destination
The communication was delayed due to a network failure in which it was unable to receive the response from a connection destination.

■Workaround

If the error does not reoccur, this was caused possibly by temporary communication failure. If it reoccurs, please try the following measures:

Timeout setting problem

Increase the timeout setting.

*Please note that for the units of values that can be set in the global resource, there are the "millisecond" adapter and the "second" adapter.

*Please refer to the help of an adapter in which the error occurred for the global resource settings.

The problem of connection destination or network environment

After checking the connection destination and the communication environment settings of DataSpider Server, please modify the DataSpiderServer so it can receive the responses from a connection destination.

Top

PKSHA FAQ logo