Tuning the web container

You can set the time that the HTTP transport channel allows a socket to remain idle between requests.

About this task

The IBM® WebSphere® Application Server web container manages all HTTP requests to servlets, JavaServer Pages and web services. Requests flow through a transport chain to the web container. WebSphere Application Server will close a given client connection after a number of requests or a timeout period. You can set a value for persistent timeouts to specify the amount of time, in seconds, that the HTTP transport channel allows a socket to remain idle between requests.

Note: The following instructions contain settings that were tested in IBM labs. These are just a starting point. Since your deployment might have a configuration unique to your site, these settings might require more adjustment.

Procedure

From the Integrated Solutions Console, click Servers > Application Servers > stadvanced_server_name > Web Container Settings > Web container transport chains > WCInboundDefault > HTTP inbound channel (HTTP_2).
Under General Properties, enter the following timeout values:
- Persistent timeout: 60
- Read timeout: 90
- Write timeout: 90
Under Persistent Connections, select Unlimited persistent requests per connection.
Click OK and save the master configuration.
From the Integrated Solutions Console, click Servers > Application Servers > stadvanced_server_name > Web container transport chains > WCInboundDefault > TCP inbound channel (TCP_2).
Under General Properties, enter the following values:
- Maximum open Connections: 60000
- Inactivity timeout: 600
Click OK and save the master configuration.
From the Integrated Solutions Console, click Servers > Application Servers > stadvanced_server_name > Web container > Session management.
Under General Properties, for the Maximum in-memory session count, enter 5000.
Click OK and save the master configuration.
If IBM Sametime® is clustered, repeat the preceding steps for each node of the cluster.