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.
How to see which Threads were running in a MID Server at a recent point in time - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • How to see which Threads were running in a MID Server at a recent point in time
KB0693277

How to see which Threads were running in a MID Server at a recent point in time


1045 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

The MID Server form has a related list of Threads currently running in the MID Server. If you had a performance problem a few days ago and have since restarted the MID Server, this will not be any use for knowing what the MID Server was doing at the time.

The data for that list is sent by the MID Servers every 10 minutes, and those ecc_queue records remain in the table for 4-5 days, so the data may still be there.



Resolution

  1. Open the ECC Queue: MID Server - ECC Queue
  2. Set the list filter for the records you are interested in:
    • Agent IS mid.server.<MID Server you are interested in>
    • Name IS MID Server XMLStats
  3. Find the record created shortly before the time you are interested in, and open it
  4. Open the XML of the Payload. 
  5. Scroll down and you will see a <threads> section, something like this:

 


Normal jobs, including Discovery probes, will run in the "Worker-Standard" thread pool. There will be one entry for each of the number of threads you have set in the MID Server parameter. 
"Worker-Standard:Idle" means the thread is free and not running anything.

You may see things running e.g. "Worker-Standard:JDBCProbe", where JDBCProbe is the probe type, and will match the value of the 'Topic' field of the ECC Queue output record for that job.



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.