JDBC Data Source "Load All Records" Times Out After Five Minutes With: "Did not get a response from the MID server" Issue Error Did not get a response from the MID server returned when an import job runs for five minutes without a reply from the MID server and thus times out. For example, this may happen when the Load All Records link is clicked in a JDBC data source: CauseBy default the JDBC request times out after five minutes due to these default settings for these system properties: glide.jdbcprobeloader.retry = 60glide.jdbcprobeloader.retry_millis = 5000 Those system properties do not exist in the sys_properties table by default, the default values are set in the platform code. The five minute timeout is calculated as follows: glide.jdbcprobeloader.retry (60 retries) x glide.jdbcprobeloader.retry_millis (5000 milliseconds (5 seconds)) = 300 seconds or 5 minutesResolutionTo extend the five minute timeout create these the two system properties as follows, this example extends the timeout from five to thirty minutes: Name = glide.jdbcprobeloader.retry Type = integer Value = 360 and Name = glide.jdbcprobeloader.retry_millis Type = integer Value = 5000 Notice that glide.jdbcprobeloader.retry_millis is not changed from the default value, but it is provided just to show the relation between the two system properties. The new timeout is 30 minutes: glide.jdbcprobeloader.retry (360 retries) x glide.jdbcprobeloader.retry_millis (5000 milliseconds (5 seconds)) = 1800 seconds or 30 minutes Adjust these properties with different values as you see fit.