(ZOS) Timeout condition resolutions

This topic gives an overview of how to resolve timeout conditions.

In such a complex environment as WebSphere Application Server for z/OS, timeouts might occur for many different reasons. Although we can alter timeout values, we should not do so until we understand why the timeout occurs. Depending on the timeout condition, we might be able to permanently fix the timeout condition by doing some system or application tuning. For example, if the diagnostic data indicates throughput problems, we can alter the number of server regions, the number of threads within each server region, or the use of replicated servers.

Generally speaking, increasing the timeout values should be your last resort, or only a temporary action taken to prevent multiple timeout-abend dumps from causing system performance problems. If we increase timeout values without properly diagnosing the timeout condition, the only results we might see are less frequent abends and dumps for the same timeout condition, or slower system or application performance.

Troubleshoot administration

Timeout properties summary