Customer testing an high number of itineration (+5000 HTTPS requests) over a keep-alive connection between performance test client and the Gateway. However, every 100 requests, the Gateway close the connection and a new one is established. Customer expectation is that keep-alive is honoured until no more requests have been transmitted and keep-live timeout is reached.
Release : 10.0
The limitation is enforced by the underlying Tomcat subsystem. In fact, by default, the maximum number of HTTP requests which can be pipelined until the connection is closed is 100.
In the Gateway Appliance, Tomcat default behaviour can be tuned in Policy Manager > "Manage Listen Ports" > "PORT" > "Advanced properties" .
The properties which is used to control the number of HTTP requests which can be pipelined is maxKeepAliveRequests (case sensitive). The property need to be added in order to change the default behaviour.
Here an example with max connection number set to 10000.
Note: Setting this to -1 will allow an unlimited amount of pipelined keep-alive HTTP requests.