Connection Management
The options on the Connection Management pages allow you to tune several important properties of proxy behavior, including connection throttling and load shedding, and individual client connection limits and rates.
By default, Content Gateway accepts 60,000 connections. A connection throttle event occurs when client or origin server connections reach 90% of half the configured limit (27,000 by default). When a connection throttle event occurs, Content Gateway continues processing all existing connections and queues new client connection requests until the connection count falls below the limit.
If you think that Content Gateway is hitting the connection limits, you should monitor the Performance graphs to get an accurate reading of connection activity. In particular, check the Active Client Connections and TCP ESTABLISHED Connections graphs. You can also check error messages in the system log file, error log file, or event log files.
| Throttling Net Connections |
Specifies the maximum number of network connections that Content Gateway accepts. The default value is 60,000. Setting a Content Gateway throttle limit helps to prevent system overload when traffic bottlenecks develop. When network connections reach this limit, Content Gateway queues new connections until existing connections close. Do not set this variable below the minimum value of 100. |
| Maximum Connections |
Specifies the maximum number of client connections allowed before the ARM starts forwarding incoming requests directly to the origin server. The default value is 1 million connections. If you change this option, you must restart Content Gateway. |
Specifies:
- Client concurrent connection limits
- Client connection rate limits
- Proxy response when a limit is exceeded
- A list of clients excepted from the limits
| Concurrent Connection Limit: Maximum concurrent connections | Specifies the maximum number of concurrent HTTP/HTTPS connections a client is allowed. The default is 1000. The supported range is: 1 - 45000 |
| Concurrent Connection Limit: Alert when limit exceeded |
When enabled, causes Content Gateway to generate an alert when a client exceeds the maximum concurrent connection limit. In addition to displaying the alert in the Content Gateway manager, it is also logged in /var/log/ messages and content_gateway.out. |
| Concurrent Connection Limit: Close excessive connections when limit exceeded | When enabled, causes Content Gateway to close excessive connections when the limit is exceeded. |
| Connection Rate Limit: Maximum connection rate | Specifies the maximum connections per second, averaged over a minute, that a client can make. The default is 100. The supported range is: 1 - 1000 |
| Connection Rate Limit: Alert when limit exceeded |
When enabled, causes Content Gateway to generate an alert when a client exceeds the maximum connection rate limit. In addition to displaying the alert in the Content Gateway manager, it is also logged in /var/log/ messages and content_gateway.out. |
| Connection Rate Limit: Close excessive connections when limit exceeded | When enabled, causes Content Gateway to close excessive connections when the limit is exceeded. |
| Exceptions |
Specifies IP addresses and/or IP address ranges to which connection limits are not applied. IP addresses can be IPv4 or IPv6 (IPv6 support must be enabled). Multiple addresses or ranges can be specified in a comma-separated list that can contain up to:
|