Extending the HTTP persistent timeout on the WebSphere proxy server

You can extend the HTTP persistent timeout on the IBM® WebSphere® proxy server to stay connected longer.

About this task

The default rtc4web timeout value is 30 seconds. This is the default timeout for the WebSphere proxy server persistent timeout setting, too. This can cause a rare condition to occur where both sides of the connection can let go at the same time. In order to minimize this conflict, extend the WebSphere proxy server HTTP Persistent timeout to stay connected longer.

Procedure

  1. Log into Integrated Solutions Console on the server where the WebSphere proxy server is configured.
  2. Click Servers > Server Types > WebSphere proxy servers .
  3. In the table listing the WebSphere proxy servers, click the link representing the proxy server you want to modify.
  4. In the Proxy Settings section, expand the HTTP Proxy Server Settings tree.
  5. Click Proxy server transports.
  6. Click HTTP_PROXY_CHAIN. It should be associated with port 80.
  7. Click HTTP inbound channel (HTTP 3) .
  8. In the General Properties section, set the Persistent timeout to 615 seconds.
  9. Select the Use persistent keep alive connections setting. Be sure the check box contains a check mark.
  10. Select the Unlimited persistent requests per connection setting. Be sure the check box contains a check mark.
  11. Click Apply, and then click Save.
  12. Navigate back to the Proxy server transports page.
  13. Click HTTPS_PROXY_CHAIN.
  14. Repeat steps 7 through step 11 of this procedure.
  15. Click Servers > Server Types > WebSphere proxy servers .
  16. Click the name of the proxy server.
  17. In the Proxy Settings section, expand the HTTP Proxy Server Settings tree.
  18. Click Proxy server transports.
  19. Click HTTP_PROXY_CHAIN. It should be associated with port 443.
  20. Click HTTP inbound channel (TCP_7).
  21. In the General Properties section, set the Inactivity timeout to 645 seconds.
  22. Click Apply, and then click Save.
  23. Navigate back to the Proxy server transports page.
  24. Click HTTPS_PROXY_CHAIN.
  25. Complete step 20 through step 22 of this procedure.
  26. Repeat for every WebSphere proxy server that you configured for the cluster.