Connection timeout is not honoured (using SSL connection)

[superbob]

Describe the issue

The connection timeout configuration (connectTimeout property) is not honoured when connecting to a pgsql database (at least through SSL).

So if the connection is slow (more than 3s to establish) it will timeout even if more than 3s is configured in the configuration property.

The SSL mode is "require" and a client certificate + client private key are used.

Driver Version?

Since 42.5.2.

It is working fine with 42.5.1.

Still present in 42.7.1.

Java Version?

Not relevant.

OS Version?

Not relevant.

PostgreSQL Version?

14.7 (Ubuntu 14.7-1.pgdg22.04+1)
Case sensitivity: plain=lower, delimited=exact
SSL: yes

To Reproduce

1. Setup a slow socket connection to a database.
   In my case I'm using a database connection protected by Cloudflare Access which asks for a confirmation through the web browser before establishing the connection. That is during this time that the timeout occurs if I take more than 3 seconds to confirm the connection in Cloudflare Access.
2. Use a driver with version >= 42.5.2.
3. Make sure to have at least 10 seconds in the connectTimeout property of the JDBC connection.
4. Try to connect to the database using DBeaver or IntelliJ or anything else.
5. Wait for more than 3 seconds (at least 5 seconds).
6. The connection will fail at approximately 3 seconds.

Expected behaviour

Depending on the connection speed:

• If it is more than 3 seconds, but less than the connectTimeout, it should succeed.
• If it lasts more than the connectTimeout, it should time out, but not before the configured timeout value.

[davecramer]

I'm guessing you need to use sslResponseTimeout which is in milliseconds. This PR #2687 seems relevant.

[vlsi]

I think connect timeout should apply to both ssl and simple connects

[davecramer]

I think connect timeout should apply to both ssl and simple connects

in which case sslResponseTimeout seems redundant

[davecramer]

Ok, so the whole SSL timeout thing seems complicated. Do we remember why we added SSL_RESPONSE_TIMEOUT?

[superbob]

Using the sslResponseTimeout property works around the issue indeed 👍. But as vlsi said, maybe connectTimeout should be honoured, even in this case (SSL).

[davecramer]

I'm going to close this as there is a work around