Configuring the HTTP connection pool
Optimize connections with external services by adjusting the number and duration of connections.
About this task
PingFederate uses an HTTP connection pool to enable HTTP communication with external systems, including PingOne communication, LDAP gateways, some PingFederate adapters, and many other functions.
Most environments won’t need to tune HTTP connection pool values.
If you find that you need to adjust timeout values, it might indicate issues with your network or overall capacity. You should investigate those configurations before you adjust these settings.
If you do need to tune the HTTP connection pool, you should adjust and test Adjust Test and adjust theses values as necessary. |
Steps
-
Open the
<pf_install>/pingfederate/server/default/data/config-store/http-connection-pooling-manager.xml
file. -
Adjust the values as detailed in the following table:
Setting Default Value Description max-connections
350
The maximum number of connections in the pool.
max-connections-per-route
100
The maximum number of connections per route (port or URL).
connection-timeout
60000
The time in milliseconds available to establish a connection with the remote host.
request-timeout
120000
The time in milliseconds available to retrieve a connection from the connection pool.
connection-idle-timeout
30000
The amount of time a connection in the pool can be idle before it is cleaned up in milliseconds.
keepalive-timeout
1000
The amount of time in milliseconds that a connection can idle before it is returned to the pool for use.
cleanup-delay-secs
10
The delay in seconds before cleaning the HTTP client cache.
-
Save and close the file.
-
Restart PingFederate
-
For a clustered PingFederate environment, repeat the previous steps on each engine node.