jct-read-inactive-timeout
Use the jct-read-inactive-timeout entry to define the number of seconds to wait for data from the junctioned WebSocket server before the connection is closed.
jct-read-inactive-timeout = seconds
Description
The jct-read-inactive-timeout entry defines the number of seconds to wait for data from the junctioned WebSocket server. If the timeout is reached, then the WebSocket connection is closed.
An inactive timeout occurs when the WebSocket application or browser attempts to read data from the socket, but none becomes available within the timeout period because the other end has not written any data to the socket. In other words, an inactive timeout is a read data operation timeout. This situation might occur because the writing end is hung or the underlying TCP/IP connection was ended without notification by a firewall. However, certain legitimate causes might also trigger the timeout. For example, during user interaction, the user takes a break before responding to the application, which might trigger this timeout.
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 for data from the junctioned WebSocket server before the WebSocket connection is closed.
Usage: Required.
Default value
120
Example:
jct-read-inactive-timeout = 120