WebSEAL worker threads
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.
We can adjust the worker threads value according to our 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.
Parent topic: Web server configuration
Related concepts
- Content caching
- Communication protocol configuration
- IPv4 and IPv6 overview
- IPv6: Compatibility support
- IP levels for credential attributes
- LDAP directory server configuration
- WebSEAL worker thread configuration
- Global allocation of worker threads for junctions
- Per-junction allocation of worker threads for junctions
- HTTP data compression
- WebSEAL data handling by using UTF-8
- UTF-8 dependency on user registry configuration
- UTF-8 data conversion issues
- UTF-8 impact on authentication
- UTF-8 impact on authorization (dynamic URL)
- Encoding type usage
- UTF-8 support for uniform resource locators
- UTF-8 support in POST body information (forms)
- UTF-8 support in query strings
- UTF-8 encoding of tokens for cross domain single signon
- UTF-8 encoding of tokens for e-community single signon
- UTF-8 encoding of cookies for failover authentication
- UTF-8 encoding of cookies for LTPA authentication
- UTF-8 encoding in junction requests
- Validation of character encoding in request data
- Set system environment variables
- Cross-Origin Resource Sharing (CORS) Support
Related tasks
- Specify the WebSEAL host name
- Modify the configuration file settings
- Configure WebSEAL for IPv6 and IPv4 requests
Related reference
- IPv6: Upgrade notes
- Allocation view of worker threads for junctions
- Supported wildcard pattern matching characters