The following properties are available for long-running SOAP requests.

Table 1. Long-running SOAP request properties
PropertyDescription
glide.http.connection_timeout Specify the maximum number of milliseconds an outbound HTTP request (such as Web Services) will wait to establish a connection.
  • Type: integer
  • Default value: 10000 (10 seconds)
  • Location: system properties [sys_properties] table
glide.http.timeout Specifies the maximum number of milliseconds to wait before an outbound transaction times out.
  • Type: integer
  • Default value: 175000 (175 seconds)
  • Location: Add to system properties [sys_properties] table
glide.soap.max_redirects Specifies the maximum number of redirects the server sends to the client before the soap request is timed out.
  • Type: integer
  • Default value: 20
  • Location: system properties [sys_properties] table
glide.soap.request_processing_timeout Specify the maximum number of seconds an inbound SOAP request has to finish processing before the connection times out. This property computes a default value from the value of the property glide.http.timeout divided by 1000.

This property accepts values 5–1200 seconds (20 minutes).

Customers might have network infrastructure (such as proxy servers) in place which implement a shorter timeout. In this case, a socket timeout may occur unless this property is set to a shorter value. Set this property to a value several seconds less than the shortest socket inactivity timeout in effect anywhere in the network path between the client application and the instance.

  • Type: integer
  • Default value: 60
  • Location: system properties [sys_properties] table
glide.soapprocessor.allow_long_running_threads Enables or disables a 307-Temporary Redirect when the request includes a redirectSupported=true parameter. The default setting is true (enabled).
glide.soapprocessor.max_long_running_threads Controls the maximum number of long-running SOAP threads which can run at any one time. The default value for this property is determined dynamically based on the number of SOAP semaphores configured. It should not be necessary to change this value.