Connection keep-alive

[serge-rider]

Connection keep-alive

[serge-rider]

[serge-rider]

Keep-alive makes huge sense if you are working in transactional mode. Disconnect ends current transaction (with rollback), all not-commited changes are lost.
Also, in some environments inactive connection timeout is very small (1-5 minutes). So Kepp-Alive feature is still very wanted by some people.
Although auto-reconnect is also a wanted feature.

[hailin84]

So, is that available to test connections periodically? We have firewall, so connections lost after a few minutes if no operation commit, it would be fine if DBeaver can test connections on idle. As I know, many Datasource can do this, like HikariCP.

[adaliszk]

Hmm, I think the autoreconnect should be better option for that, because at my Company if you just pinging the server then the whole keep-alive wont work. We have multiple databases with firebird and most of them recreaded or least restarted on each day and the server is not stoped, so the ping has a result. The restart/recreate need only a few seconds but after that he connected driver wont able to make a transaction. I think if the program detect a disconnect answer from a transation start then it can be reconnect to the database.

[adaliszk]

Oh, I did not know that the inactive time can be that small :) In that case it should be helpfull a lot this feature.

[uesleilima]

I'm looking forward this keep alive feature, my organisation firewall timeout policy is driving me crazy with my oracle connections...

[NullpointerForever]

I need this feature too :-)

[Anderseta]

Can't wait for this!

[Anderseta]

Amazing! Thank you a lot

[NullpointerForever]

Thank you :-)

[ssyang0102]

Perfect！

[sergei3000]

This is a great option! But I have two questions about how to use it.

1. Do the seconds in it show how often connection is renewed? Or do they show for how long the connection is kept alive since the last action?

2. After turning this option on and setting the number of seconds should I set a ping query in the driver's options (I'm using MS JDBC driver to connect to Azure SQL Database from Ubuntu):
   

[serge-rider]

1. The first (interval between ping query execution).
2. Usually you don't have to set ping query - by default DBeaver will use JDBC API function for pinging.
   However it can be unsupported by some drivers - in this case it makes sense.

[rsmunix]

Perfect!