The JDBC isValid() method did not handle timeouts and was throwing unexpected exceptions
Details
| Detail name | Value |
|---|---|
| Changelog Number | 21411 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.1.0, JDBC 24.0.0 |
| Fix Versions | JDBC 24.2.0 |
| Resolution Date | 2024-11-11 |
Description
What was the expected behavior
The JDBC method isValid(timeout) tells the user if the connection still can be used or not. It should return at least after the specified timeout expired. It should return false if the connection is not valid.
What was the wrong behavior in the driver
The timeout was not used. Instead another socket timeout was ending the method and throwing an exception.
Workaround
There is no workaround.
Fix
Now isValid(timeout) uses the given timeout and return true or false.
Changed behavior
Now isValid(timeout) will use the given timeout and return true or false.
