Exasol drivers no longer try to connect to all given nodes on login error
Details
| Detail name | Value |
|---|---|
| Changelog Number | 7675 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0, Exasol 6.1.0 |
| Fix Versions | Exasol 6.1.3 |
| Resolution Date | 2019-04-23 |
Background
If multiple hosts are specified in the connection string, the Exasol Drivers (ODBC, JDBC, ADO.NET, EXA-CLI) try to connect to all given nodes in random order, until one of the hosts does accept a connection.
Problem
All hosts are tried, even if one actively rejected the login after accepting a network connection.
Fix:
The driver will return an error if one connection attempt is actively rejected by the server. Possible reason for this is an authentication failure.
If no socket connection can be established for reasons like: "connect timeout", "connection refused", the driver will still try to connect to the other hosts form the connection string.
