Memory leak if TLS connections cannot be established
Details
| Detail name | Value |
|---|---|
| Changelog Number | 16674 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.0.0, Exasol 7.1.0, Exasol 8.0.0 |
| Fix Versions | Exasol 7.1.19, Exasol 8.13.0 |
| Resolution Date | 2023-03-21 |
Description
In some cases if an incoming TLS connection cannot be established (for example a client disconnect or the client and server cannot mutually agree on cryptographic algorithms and keys), a memory leak may occur. Over time, this leak may become significant and cause the database to crash.
Workaround
Restarting the database will clear the memory leak, but does not prevent it from occurring again.
Fix
The memory leak caused by failed TLS connections no longer occurs.
