Client disconnect while fetching data may cause improper session cleanup
Details
| Detail name | Value |
|---|---|
| Changelog Number | 26129 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASolution 5.0.0, Exasol 8.29.0, Exasol 2025.1.0, Exasol 2026.1.0 |
| Fix Versions | Exasol 2026.1.2, Exasol 2025.1.16 |
| Resolution Date | 2026-08-28 |
Description
If a client disconnects from Exasol while fetching a result set, then the session may not be cleaned up properly. Specifically, the session could still be shown to have the FETCH DATA status in the EXA_DBA_SESSIONS table and not have a LOGOUT_TIME in the EXA_DBA_AUDIT_SESSIONS table. Such a session could also hold object locks.
Workaround
Avoid disconnecting the client from Exasol while fetching data.
Fix
A fix has been implemented to ensure that disconnected sessions are cleaned up properly.
