Global allocation of worker threads for junctions

We can modify the entries in the [junction] stanza of the WebSEAL configuration file to control the global allocation of worker threads across all junctions for a particular WebSEAL server. The values used for these stanza entries are expressed as percentages within the range of 0 to 100.

• worker-thread-soft-limit

  Send a warning before the hard limit is reached. When the worker-thread-soft-limit is exceeded, warning messages are sent, every 30 seconds, to the WebSEAL error log file. For example, when worker-threads = 50, a setting of 60 (%) causes warning messages to be displayed when the junction uses more than 30 worker threads. All requests above 30 worker threads are still processed until the hard limit is reached. Default is 90 percent.

• worker-thread-hard-limit

  Cut-off point for servicing requests across a junction. When the worker-thread-hard-limit is exceeded, error messages are sent, every 30 seconds, to the WebSEAL error log file. In addition, the user is sent a 503 Service Unavailable message. For example, when worker-threads = 50, a setting of 80 (%) causes error messages to be displayed when the junction tries to use more than 40 worker threads. All requests that represent greater than 40 worker threads on the junction are returned with a 503 Service Unavailable message. The default value of 100 (%) indicates there is no limit.

These global settings apply equally to all configured junctions. When configuring these two stanza entries, it is logical to set the soft limit to a lower value than the hard limit.

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
• WebSEAL worker threads
• 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