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.
MID Server is not processing JDBCProbe requests / ECC Records. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • MID Server is not processing JDBCProbe requests / ECC Records.
KB0716634

MID Server is not processing JDBCProbe requests / ECC Records.


3071 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


MID Server is not processing JDBCProbe requests

Release


Kingston Patch 10 and Lower

Cause


When we have a MID Server which is making a JDBC connection, Under certain condition, when one multiple JDBC Probes are executing at the same time and they happen to load their respective drivers, deadlock at the native level can occur

 

We added MID Debug parameter 
https://docs.servicenow.com/csh?topicname=mid-server-parameters.html&version=latest 

After that we can see the error - 

10/05/18 12:28:35 (556) ECCQueueMonitor.5 DEBUG: STANDARD threadpool queue is full! Skipping this message (will try again later). 
10/05/18 12:28:35 (556) ECCQueueMonitor.5 DEBUG: Event: GenericCounterMetricEvent 
10/05/18 12:28:35 (556) ECCQueueMonitor.5 DEBUG: Skipped message: Command /ms/dist/entmgt/PROJ/netcoolusers/prod/common/bin/nco_alert -Manager ServiceNow -Agent '${agent}' -AlertGroup '${alert_group}' -AlertKey '${alert_key}' -Severity ' 
${severity}' -Summary '${summary}' 4778e490db056784056d79578c9619eb 
10/05/18 12:28:35 (556) ECCQueueMonitor.5 DEBUG: Number of messages added to threadpool queue in current polling cycle: 0 


We are looking at the error as - STANDARD thread pool queue is full! Skipping this message (will try again later). 

We see the stack trace in the mid server thread is below 

| at com.service_now.mid.connections.jdbc.JDBCConnection.establishConnection(JDBCConnection.java:97) 
| at com.service_now.mid.connections.jdbc.JDBCConnection.connect(JDBCConnection.java:74) 
| at com.service_now.mid.connections.jdbc.JDBCConnectionFactory.create(JDBCConnectionFactory.java:52) 
| at com.service_now.mid.connections.ConnectionCachePool.getAvailableConnection(ConnectionCachePool.java:82) 
| - locked <0x00000000c2626700> (a com.service_now.mid.connections.ConnectionCachePool) 
| at com.service_now.mid.connections.ConnectionCache.get(ConnectionCache.java:94) 
| at com.service_now.mid.probe.JDBCProbe.getJDBCConnection(JDBCProbe.java:710) 
| at com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:107) 
| at com.service_now.mid.probe.AProbe.process(AProbe.java:81) 
| at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:123) 
| at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20) 
| at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 

Resolution


0. Bring down MID Server

1. Cleanup all old JDBC Probes record [ set the ECC records state as 'error' ]

2. Import script include [which is in the attachement]

3. Run the script to load the drivers using Background scripts
This will allow us to set the priority of the drivers load message to "interactive". The modified script include is attached to this Task. The script below sets the priority to 0: 

var midName = 'thanh-eclipse'; // Name of the MID Server
var jspr = new JavascriptProbe(midName); 
jspr.setName('LoadJDBCDrivers'); 
jspr.setPriority('0'); 
jspr.addParameter('skip_sensor', 'true'); 
jspr.setJavascript('Packages.java.sql. DriverManager.getDrivers();'); 
jspr.create(); 

We should also create either a business rule or a script action to automatically run this script when a MID server is down. That way, when it comes back up, the message is there for it to load the drivers. 

4. Restart MID Server

5. Run the JDBC Integration


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

No attachments found

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.