Exasol may not be able to accept connections anymore caused by hanging metadata requests
Details
| Detail name | Value |
|---|---|
| Changelog Number | 5782 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0 |
| Fix Versions | Exasol 7.0.0, Exasol 6.1.9, Exasol 6.2.5 |
| Resolution Date | 2020-09-11 |
Since Exasol 6.0.0 metadata requests like in JDBC DatabaseMetaData.getColumns() are handled by the connection server for a session without a sql process. For this a driver with version >= 6.0.0 is needed.
If the reply for this metadata request is hanging during writing to the socket, no new logins can be performed after a while.
Restart of the database is needed to be able to perform logins again.
Workaround
You can force the driver to send metadata requests as SQL. For this add the following parameter to the connection string:
JDBC: metadataSQL=1
ODBC: LEGACYCATALOG=Y
