A liveness packet is sent periodically across a client/server TCP/IP communications protocol to confirm that a connection
is intact. If the server runs for a LivenessTimeout period (default 2 minutes) without detecting a liveness packet on a connection,
the communication is severed, and the server drops the connection associated with that client. Unix non-threaded clients and
TDS connections do not do liveness checking.
The -tl option on the server sets the LivenessTimeout value for all clients that do not specify a liveness period.
Liveness packets are sent when a connection hasn't sent any packets for between one third and two thirds of the LivenessTimeout
When there are more than 200 connections, the server automatically calculates a higher LivenessTimeout value based on the
stated LivenessTimeout value, so the server can handle a large number of connections more efficiently. Liveness packets are
sent between one third and two thirds of the LivenessTimeout on each idle connection. Large numbers of liveness packets aren't
sent at the same time. Liveness packets that take a long time to send could be sent after two thirds of the LivenessTimeout.
A warning appears in the database server message log if the liveness sends take a long time. If this warning occurs, consider
increasing the LivenessTimeout value.
Although it isn't generally recommended, you can disable liveness by specifying the following:
dbsrv12 -tl 0 -n my_server
Rather than disabling the LivenessTimeout option, consider increasing the value to one hour as follows: