EXA-to-EXA IMPORT/EXPORT May Hang or Fail in Certain Scenarios
Details
| Detail name | Value |
|---|---|
| Changelog Number | 28073 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.32.0 |
| Fix Versions | Exasol 2026.1.1, Exasol 2025.1.13 |
| Resolution Date | 2026-07-15 |
Description
In certain scenarios, Exasol EXA-to-EXA IMPORT/EXPORT operations may hang or fail due to an internal issue in the IMPORT/EXPORT mechanism.
The problem might surface as different user-facing errors:
ETL-4005: An error occured while creating connection to external EXASolution. [ETL-4005: An error occured while creating connection to external EXASolution. [sslreadtimeout: SSL sslreadtimeout: connection closed by remote host (Session: ...) Error receiving message from Exasol. Socket failure. (Session: ...) Error code was 0 Server communication error. No server listening. Error request parallel connections.]] ETL-4005: An error occured while creating connection to external EXASolution. [ETL-4005: An error occured while creating connection to external EXASolution. [Connection lost.]]
Workaround
Switch to Legacy Parallel Connection mode as described in:
CHANGELOG: Introducing Configurable Legacy Parallel Connection Mode for Exa-to-Exa Operation
Fix
The underlying internal issue causing EXA-to-EXA IMPORT/EXPORToperations to hang or break in specific cases has been fixed. IMPORT/EXPORT jobs now complete successfully without requiring the legacy mechanism.
