This problem presents itself because the default settings
for the Web container I/O timeout and keep alive timeout have been set too
low.
There are three options to pursue when facing this issue:
- Use a threaded Web server such as IBM® HTTP Server 2.0.
This issue has primarily been observed when using a process-based Web
server such as IBM HTTP Server 1.3.26.
- Disable the use of the keep alive connections by setting
the value for Maximum keep alive to 0.
- Tune the values for KeepAliveTimeout and I/O TimeOut. The
default values are 5 seconds. We have suggested testing values between 15
and 60 seconds for optimum performance.
To change the values in 4.0
From the administrative console, select Application Server >
Services > Web Container Service > Edit Properties > Transport
Tab
To change the values in 5.0
- Access the settings page for a property of the transport:
- In the console navigation tree, click Servers > Application Servers
> server_name > Web Container > HTTP Transports >
transport_host_name > Custom Properties.
- On the Custom Properties page, click New.
- On the settings page for a property, specify the transport property
name and the value.
- For example, specify a name of MaxKeepAliveConnections and a value 0.
- Click OK.
- To modify the I/O timeout use ConnectionIOTimeout as the
name.
- To modify the keep alive timeout use
ConnectionKeepAliveTimeout as the name.
- Click Save on the console taskbar and save the changes to the
configuration.
- Restart the server.
|