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 execution fails with "Did not get a response from the MID server" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • JDBC Data Source execution fails with "Did not get a response from the MID server"
KB0858700

JDBC Data Source execution fails with "Did not get a response from the MID server"


5808 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Instance times out waiting for the MID Server to respond on a JDBC  Data Source execution  - "Did not get a response from the MID server"

Cause

There are JDBC data sources on the instance that have "Connect timeout" and "Query Timeout" set to '0' indicating there is no timeout.
When the actual database is unresponsive the threads on the MID Server that are executing these JDBC probes hang and MID Server does not execute any more JDBC data sources.

This affects the performance of the MID Server and the instance to timeout on the JDBC  data source executions with "Did not get a response from the MID server"



Resolution

We need to follow these steps to kill the JDBCProbe threads:

1) On the ECC Q find all the JDBCProbe  'output' records in state=processing
2) Set all of them to state=error
3) Restart the MID Server


To prevent this issue from happening it is recommended to set Connect timeout and Query timeout values for all the JDBC data sources.


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?

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.