ODBC Error Messages: Determining if you need to reduce the value of timeout settings
- driver not loading
- driver times out waiting for a response
If you receive an error message during a query indicating that the ODBC driver timed out waiting for a response, this is likely caused by overly aggressive proxy server or firewall socket inactivity timeout settings.
If you receive the following error message when running a query, ERROR [HY000] [DataDirect][ODBC Open Access SDK driver][OpenAccess SDK SQL Engine] Error running query for execute: The ODBC driver timed out waiting for a response. This is often caused by overly aggressive proxy server or firewall socket inactivity timeout settings. You may need to set instance property glide.soap.request_ processing_timeout to a smaller value. Error Message: Socket timeout , this indicates that the driver timed out during a long-running query and you can set the instance property to a smaller value to prevent this from happening again.
Create an integer property on the instance called glide.soap.request_processing_timeout and set the value to 28 seconds. (This is based on the 30 second socket inactivity timeout value.)
This new setting causes the SOAPProcessor to perform a temporary HTTP redirect after 28 seconds to keep the connection alive while the long-running query is executing on the instance.