clt-write-blocked-timeout
Use the clt-write-blocked-timeout entry to define the number of seconds to wait while WebSEAL is blocked sending data to the WebSocket client before the connection is closed.
clt-write-blocked-timeout = seconds
Description
The clt-write-blocked-timeout entry defines the number of seconds to wait while WebSEAL is blocked sending data to the WebSocket client or browser. If the timeout is reached, then the WebSocket connection is closed.
A blocked timeout occurs when the WebSocket application or browser writes to a socket, but the socket has a full write data queue due to the other end not reading the data. In other words, a blocked timeout is a write data operation timeout. This situation might occur because the reading end is hung. However, certain legitimate causes might also trigger the timeout. For example, the effective data bandwidth of the connection to the remote end is smaller than the rate at which data is being generated.
Set this timeout value to be higher than any timeout that each WebSocket application might employ, allowing the WebSocket client and server components to deal with timeouts themselves. This option is useful in setting an upper limit to help ensure that malicious attacks or unexpected errors cannot permanently consume all the WebSEAL WebSockets resources.
Options
seconds The number of seconds to wait while WebSEAL is blocked sending data to the WebSocket client or browser before the connection is closed.
Usage: Required.
Default value
120
Example:
clt-write-blocked-timeout = 120