We have a TDV web service that takes more than 60 seconds to return data. When a client invokes the web service, the client fails after 60 seconds with a SocketTimeoutException.

When a request to a TDV web service takes more than 60 seconds to return data, it fails with a SocketTimeoutException

Please use the checklist below:

(1) Server level timeout 
Ensure that Studio >> Administration >> Configuration Server >> Runtime Processsing Information >> Sessions >> Session Timeout is set to more than 60 seconds. By default, the session timeout is set to 1800 seconds.

(2) Data source level timeouts
If the web service relies on a data source, the request may be timing out at the data source.

(i)  Verify that the data source is not configured with a timeout of less than 60 seconds, as follows.

• Open the data source
• Go to the Advanced Panel of the data source
• Inspect the value of the Execution Timeout(s) setting on the panel

(ii) Review the data source timeout settings under Studio >> Administration >> Configuration >> Data Sources >> Common to Multiple Source Types

(3) Client level timeout
If the problem still persists, it is likely that your client application is timing out the request (by default, some clients will time out a request after 60 seconds). Check your client application timeout setting. Below is an example that illustrates a SocketTimeoutException occurring in a client (SoapUI) after 60 seconds when the TDV web service takes 75 seconds to respond. The example shows that after increasing the timeout setting in SoapUI to a value greater than 60 seconds, the same request started executing successfully.