Configure Timeouts for Managed Omni Gateway
Omni Gateway offers these timeouts to improve service quality and reduce computing resource waste:
-
Stream Idle Timeout
The Stream Idle Timeout enables you to set a maximum amount of a time a stream can remain idle without receiving any data in either the inbound (client to Omni Gateway) or outbound (Omni Gateway to upstream service) direction.By default, all Omni Gateway API instances have a stream timeout of 300 seconds.
-
Upstream Idle Timeout
The Upstream Idle Timeout enables you to set a maximum amount of time a stream between Omni Gateway and the upstream service can remain idle between requests.By default, all Omni Gateway API instances have an upstream idle timeout of 60 seconds.
-
Response Timeout
The Response Timeout enables you to set a maximum amount of a time Omni Gateway waits for a response from an upstream service. The timeout time starts at the last request sent by Omni Gateway.By default, all Omni Gateway API instances have a response timeout of 15 seconds.
You can configure these timeouts for Managed Omni Gateway via:
-
Managed Omni Gateway deployment: Set initial timeout values when you create the gateway.
-
Runtime Manager runtime configurations: Applies to all API instances in the gateway after the gateway is deployed.
-
Policy: Applies to one API instance or upstream and provides granular control.
Configure Timeouts During Managed Gateway Deployment
Set timeout values in the deployment flow when you create a Managed Omni Gateway. For the UI steps and parameter descriptions, see Deploy a Managed Omni Gateway.
Configure Timeouts in Runtime Manager
-
In Anypoint Platform, select Runtime Manager.
-
Select Omni Gateways.
-
Select your Omni Gateway.
-
Open Runtime Configurations.
-
Open Timeouts.
-
Set values for Stream Idle Timeout, Upstream Connection Idle Timeout, and Upstream Response Timeout.
-
Apply the changes.