Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
JDBC Data Source "Load All Records" Times Out After Five Minutes With: "Did not get a response from the MID server" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • JDBC Data Source "Load All Records" Times Out After Five Minutes With: "Did not get a response from the MID server"
KB0684496

JDBC Data Source "Load All Records" Times Out After Five Minutes With: "Did not get a response from the MID server"


5324 Views Last updated : May 22, 2024 public Copy Permalink
KB Summary by Now Assist

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: 

Cause

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

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


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • Screen Shot 2018-04-17 at 11.43.13 AM.png

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.