Connectiontimeout and loadbalancetimeout settings for ODBC driver Policy Server settings
Article ID: 136252
Updated On:
Products
Issue/Introduction
Will the Policy Server registry key "ConnectionTimeout" close an unresponsive connection with the ODBC backend server instead of setting the DataDirect driver LoadBalanceTimeout?
Environment
All Policy Server versions with DataDirect ODBC driver
Resolution
The "LoadBalanceTimeout" feature is at the DataDirect level, and this manages the connections at the network level to the database.
The "ConnectionTimeout" is at the application level, when the Policy Server sends a request to the database as selected, etc.
Both parameters and keys are not handling the same use case.
The DataDirect Driver "LoadBalanceTimeout" will handle the idle timeout of the connection, and the Policy Server key ConnectionTimeout handles unresponsive connections (1)(2)(3).
So, if a connection has been broken, or the ODBC server takes time to answer to the Policy Server query, then the ConnectionTimeout may apply.
But the LoadBalanceTimeout won't apply in this situation because the Policy Server tries to use the connection, and as such, the connection is not idle.
So said, the timeout is maintained at the connection level on the driver side, and at the query level at the application level which is the Policy Server.
There is no equivalent Policy Server registry key configuration to handle the ODBC driver connection idle time.
Additional Information
Feedback
