pjscallSocketTimeout

This setting controls the lifetime of WebSocket connections from the PJSCALL command/program and Profound.js proxy programs to the Profound.js server.

The IBM i-side programs/commands keep the WebSocket connection open for the duration of the activation group. If the IBM i job becomes idle, this can result in the connection remaining open for long periods of time. This setting controls the time after which the server will close the connection if there is no activity on the socket.

The IBM i programs/commands will automatically reconnect if the job becomes active again after the server closes the connection. The purpose of this option is just to allow the server to cleanup long idle or potentially broken connections.

The value is specified in milliseconds, the default value is 600000 (10 minutes).

Note: This setting is for advanced use only. The default value should be optimal in most scenarios.

Example:

Auto-Alignment with timeout Setting

As of Profound.js Version 7.31.0, if pjscallSocketTimeout is not explicitly set, it will automatically align with the timeout setting (converted from seconds to milliseconds).

For Example:

• If timeout is set to 7200, then pjscallSocketTimeout will default to 7200000 (2 hours).

• If neither setting is specified, the default remains 600000 (10 minutes).

In previous versions, pjscallSocketTimeout always defaulted to 600000 (10 minutes) regardless of the timeout setting. This could cause Profound.js call request interrupted errors in proxy mode when user idle time exceeded 10 minutes. With auto-alignment, the WebSocket timeout now matches the session timeout automatically, preventing these interruption errors.