ODBC queries timing outIssue ODBC driver query fails with the following message when retrieving large dataset from the instance.ErrorMsg: [SN][ODBC ServiceNow driver][OpenAccess SDK SQL Engine]Cannot execute the query.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 timeoutResolutionODBC makes SOAP calls on the instance.If an inbound SOAP request is failing with Socket timeout since the processing time is longer than 30 secs(socket timeout)we can handle this as follows:1) Set the glide.soap.request_processing_timeout OR glide.soap.request_processing_timeout.odbc (which will only apply this to the ODBC driver) value to 28 secs Location: system properties [sys_properties] tableType: integerDefault value: 60If it does not exist in system properties add it and set the value to 28.NOTE: Make sure the request includes a redirectSupported=true URL parameter and the Request is session-aware (supports HTTP cookies).With this in place Web services clients receive a 307-Temporary Redirect to keep long sessions alive and prevent a timeout due to socket inactivity. A 307-Temporary Redirect causes web services clients which support the status code to repeat their last request to the location specified in the HTTP location header. The value of the location header sent by ServiceNow is the same URL that the web services client originally specified. The use of 307-Temporary Redirects is WS-I compliant.2) The number of redirects is controlled by glide.soap.max_redirects. Set this to a value to dictate what is the maximum processing time you want to set on the instance.The SOAP request does not timeout until the number of redirects has exceeded the value set by glide.soap.max_redirects. For example if glide.soap.max_redirects is set to 20, then the maximum processing time allowed will be (glide.soap.request_processing_timeout) * (glide.soap.max_redirects) = 28*20 = 560 secsYou will need to choose an appropriate value for this property.A SOAP request(ODBC query) that takes less than 560 secs will be successful and one that takes longer than 560 secs will get HTTP 408. NOTE: The property glide.soapprocessor.allow_long_running_threads should be 'true' and by default it is 'true'