WebSEAL draws from its pool of worker threads to process multiple requests. Worker threads handle incoming requests to applications on multiple junctioned back-end servers.
However, the worker thread pool can be quickly drained if a particular back-end application is unusually slow when it processes a high volume of requests. A depletion of the worker thread pool by this one application renders WebSEAL incapable of responding to requests for services on the remaining junctioned application servers.
When no worker threads are available to handle incoming requests, users experience a WebSEAL server that is not responding.
You can adjust the worker threads value according to your WebSEAL implementation. The number of worker threads available to WebSEAL is specified by the worker-threads stanza entry in the WebSEAL configuration file.
The configuration mechanism maintains a fair distribution of worker threads across all junctions and prevents depletion of the worker thread pool by any one junction. This configuration also prevents any application from claiming more than its share of worker threads.
To configure the allocation of WebSEAL worker threads across multiple junctions, see Global allocation of worker threads for junctions.
To configure the allocation of WebSEAL worker threads for every junction, see Per-junction allocation of worker threads for junctions.