Devart Forums

I have found strange behaviour with SSL connections (using the last version of Postgresql provider). I connect to a remote Postgresql server and without SSL it works fine. Whet I turn the SSL on, it works only if I work "very quickly", ie when I do make some sort of database communication every few seconds. If I am idle for some 10 seconds or even less, the error "Socket not connected" appears. This behaviour occurs when using connection pooling. Without it, it works fine, but the overall performace is slow due to the fact that I use connecion.open, some action, connection.close approach.
It seems to me that normal connections are kept alive while SSL are not. Is it a bug or a matter of tweaking the pool or TCPIP stack?
Thanks for reply.

We have reproduced the problem. We will investigate it and notify you about the results as soon as possible.

As a temporary workaround, please add to your connection string the Connection Timeout=0; entry.

The "SSL socket not connected" bug is fixed in the latest 4.55.39 version of dotConnect for PostgreSQL. Please try it.