Configurable Parallel Session Token Timeout for Enhanced Subconnection Flexibility
Details
| Detail name | Value |
|---|---|
| Changelog Number | 26609 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | Exasol 2025.1.2, Exasol 2025.2.0 |
| Resolution Date | 2025-08-20 |
Background
In previous versions (DB 8.32+), the parallel session token validity for subconnection establishment in parallel connections was set to a fixed duration of 60 seconds, which could not be modified by users.
This limitation created challenges for scenarios where client systems took longer than 60 seconds to establish a subconnection due to network latency, processing delays, or other reasons. In such cases, the client failed to establish the subconnection, resulting in the exception:
Parallel session has expired
To address this rigidity, a mechanism has been introduced that allows users to configure the token validity period, providing greater flexibility for diverse operational environments.
Improvement
A new database parameter parallelSessionTokenTimeout has been introduced. This allows users to customize the validity period for parallel session tokens, enabling a more adaptable approach to subconnection handling.
Details
- Database Parameter:
- Behavior:
- Name: parallelSessionTokenTimeout
- Accepted Values:
- Integer (unit: seconds)
- Default: 7200 seconds (2 hours)
- Minimum allowed value: 0
- If the parameter value is set to 0, the parallel session token timeout will be deactivated (no expiration).
- If the parameter value is less than 0, an exception will be thrown, and the database startup will be aborted with the following error message:
Parallel Session token timeout should be greater than or equal to 0. Provided value: X.
Example:
Parallel Session token timeout should be greater than or equal to 0. Provided value: -10.
Example Usage
- Default Behavior (7200 seconds):
No configuration changes; the parallel session token is valid for 2 hours. - Extending Token Timeout:
If users wish to configure a higher validity period, they can update the parameter in the database configuration as follows: - Deactivating Token Timeout:
To deactivate the token expiration entirely: - Invalid Value Example:
If a user configures an invalid value (e.g., parallelSessionTokenTimeout=-10), the database startup aborts with the error:
-parallelSessionTokenTimeout=14400
(Token will be valid for 4 hours.)
-parallelSessionTokenTimeout=0
Parallel Session token timeout should be greater than or equal to 0. Provided value: -10.
This improvement gives users precise control over the parallel session token validity period, addressing issues caused by rigid timeout behavior in previous versions, and enabling smoother operation in environments with varied client performance.
