Skip to main content
The method calls in your client library result in SOAP calls to the Subscribe Web service hosted on Vindicia servers. You can configure the method calls to wait for a response from the server for no longer than a fixed, maximum amount of time. Each client library contains a global setting for the timeout value. The optimal value of the timeout depends on the amount of data you are fetching from Subscribe in a single call, and other factors, such as server load and network latencies. Calls that are not designed well often result in timeouts. For example, a single Transaction.fetchDeltaSince() call might fetch many results. To avoid data overload, set the paging parameters to page through the set when making the call. If you are experiencing frequent timeouts, examine the nature of the call you are making and determine if you can reduce the size of the result set returned by the call. If not, raise the timeout value for your client library.

​
In PHP

In the PHP library, edit the Const.php file in the Vindicia/Soap directory to change the value of the global constant VIN_SOAP_TIMEOUT. This value is in seconds and is set to 60 by default. To change the value, type:

​
In Java

In Java, set the global SOAP timeout for Subscribe API calls in the Java library. The setting is in the com.vindicia.client.ClientConstants class with a default value of 2,500 milliseconds. To change this value, type:

​
In ASP, VB, and C++

The VindiciaCOM.dll file for ASP, VB, and C++ contains the VindiciaCOM object. That object supports the method SetTimeout(), for which you can specify the desired global SOAP timeout in milliseconds. The default is 2,500 milliseconds.

​
In C#

In C#, set the SOAP timeout globally (in milliseconds) using the SetTimeout method to the Vindicia.Environmentclass. Local timeouts may be set individually, when you instantiate the object in the C# client.
Parent topic:Support for Development