persistent-con-timeout
persistent-con-timeout = number_of_secondsDescription
Maximum number of seconds a persistent connection can remain idle in a cache before the connection is cleaned up and closed by WebSEAL.
Use an integer value lower than the configured maximum connection lifetime for the junctioned web server. For example, the connection lifetime for a junctioned Apache web server is controlled by the KeepAliveTimeout configuration entry.
We can customize the persistent-con-timeout configuration item for a particular junction by adding the adjusted configuration item to a [junction:{junction_id}] stanza.
where {junction_id} refers to the junction point for a standard junction (including the leading / character) or the virtual host label for a virtual host junction. If we do not use an integer value lower than the connection lifetime on the junctioned web server, we might encounter the following problem.
If the [junction] max-cached-persistent-connections configuration entry is set to a value greater than zero, WebSEAL reuses its TCP/IP session with the junctioned back-end server. If the junctioned back-end server closes the socket at the same time that WebSEAL starts to use this session to send a request, the request fails.
To send the request again, WebSEAL opens a new TCP/IP session. If the request body is larger than the size that WebSEAL can cache, WebSEAL fails to resend the request and generates a 500 error.
Options
number_of_seconds Integer value that indicates the maximum number of seconds a persistent connection can remain idle in a cache before the connection is closed by WebSEAL. The minimum value is 1. WebSEAL does not impose a maximum value.
Usage:
This stanza entry is required.
Default:
5
Example:
persistent-con-timeout = 5Parent topic: [junction] stanza