HTTP Connection Management Properties

  • Release version: Zurich
  • Updated July 31, 2025
  • 1 minute to read

    • Connection pooling is controlled by three properties.

    The default values for these properties are appropriate for most customers. The Glide properties are dynamic, meaning that changes to these properties will take effect immediately. No outage or restart is required to update the values.

    Property Description Default Value

    glide.http.connection_mgr.max_connections

    Controls the total number of permitted HTTP(S) connections outbound from the base system instance. This is an instance-wide value.

    		 20

    glide.http.connection_mgr.max_connections_per_host

    Controls how many of the glide.http.connection_mgr.max_connections can communicate in parallel with any particular host. If the maximum setting for any of these values is reached during normal operations, a script or background thread may have to wait briefly to obtain a connection.

    		 4
    glide.http.outbound.max_timeout The max timeout in seconds to wait for SOAPMessageV2 and RESTMessageV2 when using executeAsync method. The maximum value allowed is 30 seconds. If this value is set to something higher than 30 seconds, it will default to 30 seconds. To set a value greater than 30 seconds, see the glide.http.outbound.max_timeout.enabled property. 30
    glide.http.outbound.max_timeout.enabled Determines whether a configurable hard maximum wait time is enforced for SOAPMessageV2 and RESTMessageV2 when using executeAsync method.

    If this property is set to false, the default response timeout is five minutes.

    If this property is set to true, the value of glide.http.outbound.max_timeout is used unless a value is also passed in the waitForResponse() method, in which case the lower value of the two is used.

    You can set max response timeouts greater than 30 seconds by setting this property to false and configuring the following additional properties:
    • RESTResponseV2: Set glide.rest.outbound.ecc_response.timeout to the required system default response timeout (in seconds).
    • SOAPResponseV2: Set glide.soap.outbound.ecc_response.timeout to the required system default response timeout (in seconds).
    Then, you can use the waitForResponse() method for custom response timeouts.
    		 true

    glide.http.use_connection_mgr

    Switches connection pooling on and off. To disable the new behavior (not recommended) set glide.http.use_connection_mgr to false.

    		 true