66 views

Symptoms


With a JDBC data source, selecting the Related Link Load All Records. The job runs for five minutes and then times out with Did not get a response from the MID server:

 

Release


Applicable to all releases.

 

Cause


By default the JDBC request times out after five minutes due to these default settings for these system properties:

glide.jdbcprobeloader.retry = 60
and 
glide.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 minutes
 

Resolution


To 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. 

Article Information

Last Updated:2018-04-18 05:32:23
Published:2018-04-18