Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

HTTP Client Connection Management

Log in to subscribe to topics and get notified when content changes.

HTTP Client Connection Management

Outbound HTTP(S) connections from a base system instance or inbound connections from MID Servers, the ODBC driver, and other clients are maintained and reused where possible.

Connection pooling is used to keep track of HTTP(S) client connections to determine if they are alive and available for reuse.

ServiceNow HTTP client code means:

  • Any application or script which makes outbound HTTP(S) requests from a base system instance.
  • ServiceNow code in the MID Server or the ODBC driver which makes HTTP(S) requests to one or more base system instances.
Note: This discussion does not apply to browser-to-instance communication. No changes have been made with respect to the management of HTTP(S) connections for browser-based communication with ServiceNow. This discussion also does not apply to customer-developed Web Services clients making requests to ServiceNow.

What Should the Customer Do?

Users should monitor performance, such as the decreased time for loading Discovery data and improved ODBC driver performance. For systems with an unusually large amount of simultaneous outbound HTTP(S) activity, such as numerous third-party integrations or high-volume automated activities which generate HTTP(S) requests from the base system instance to other places, review the max_connections and max_connections_per_host properties to ensure that the settings are sufficient. This enhancement has no impact on end-user connections from browsers and no impact on connections from customer-developed Web Services client applications.