HTTP Keep alive for HTTP Routing assertion is maintaining the connection pool longer than expected

Products

• API SECURITY

Issue/Introduction

The Arcot team is using the API Gateway version 10.1 cr3 in our production environment and we are trying to control the time an outbound idle connection in the pool is maintained. We have played with changing the setting io.httpConnectionIdleTimeout from 5s to 3s but when we do network traces we find that the encrypted alert from our gateway is seen taken coming from within 500 ms to 3 seconds to reap the connection. We are trying to get a more prescriptive time between the CWP setting and when the gateway will close down the connection. It appears connections 'only clean the connection pool lazily"

https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-ga[…]balancer-best-practices/issues-in-http-load-balancing.html

Environment

Release : 10.1

Resolution

There are Cluster Wide properties that will make the gateway close IDLE connection more aggressively. 

Several tests time range to close between 3.8 to 4.1

io.httpConnectionIdleTimeout set to 3500ms

io.httpConnectionIdleInterval 1s

io.staleCheckCount 5

Restart of the gateway process should be done after these changes