Chapter 9. Tuning WebSphere for Content Manager 271
How to view or set
1. Open the administrative console; select the application server you are tuning.
2. Under Additional Properties, click Web Container.
3. Under Additional Properties, click HTTP Transports.
4. Click the port_number link in the Host column.
5. Under Additional Properties, click Custom Properties.
6. Click New.
7. In the Name field, enter MaxKeepAliveConnections.
8. Enter the value in the Value field.
9. Click Apply or OK.
10.Click Save.
Our recommendation
The value should be at least 90% of the maximum number of threads in the Web
container thread pool. If it is 100% of the maximum number of threads in the Web
container thread pool, all of the threads could be consumed by keep-alive
connections, leaving no threads available to process new connections.
9.5.5 Maximum requests for a connection (MaxKeepAliveRequests)
The maximum number of requests that are allowed on a single keep-alive
(persistent) connection. This parameter can help prevent denial of service
attacks when a client tries to hold on to a keep-alive connection. The Web server
plug-in keeps connections open to the application server as long as it can,
providing optimum performance.
Set the value to zero to allow an unlimited amount.
Default values
No default setting
How to view or set
1. Open the administrative console. Select the application server you are tuning.
2. Under Additional Properties, click Web Container.
3. Under Additional Properties, click HTTP Transports.
4. Click the port_number link in the host column.
5. Click Custom Properties under Additional Properties.
6. Click New.
7. In the Name field, enter MaxKeepAliveRequests.
8. Enter the value in the Value field.
9. Click Apply or OK.
10.Click Save.
Get Performance Tuning for Content Manager now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
