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.
Discovery failed with exceptions: java.lang.IllegalArgumentException: Missing required parameter ip_address - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Discovery failed with exceptions: java.lang.IllegalArgumentException: Missing required parameter ip_address
KB0690885

Discovery failed with exceptions: java.lang.IllegalArgumentException: Missing required parameter ip_address


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

Issue

Symptoms


There are Java exceptions in discovery logs for Network devices(Routers and switches).

java.lang.IllegalArgumentException: Missing required parameterip_address
at com.service_now.mid.probe.shazzam.scanners.APortScanner.getParamAsIP(APortScanner.java:208)
at com.service_now.mid.probe.shazzam.scanners.APortScanner.init(APortScanner.java:56)
at com.service_now.mid.probe.shazzam.scanners.AUDPPortScanner.init(AUDPPortScanner.java:35)
at com.service_now.mid.probe.shazzam.scanners.DNS.init(DNS.java:63)
at com.service_now.mid.probe.DNS.addScanners(DNS.java:140)
at com.service_now.mid.probe.DNS.processChunk(DNS.java:114)
at com.service_now.mid.probe.ShazzamBase.syncProcessChunk(ShazzamBase.java:71)
at com.service_now.mid.probe.DNS.probe(DNS.java:90)
at com.service_now.mid.probe.AProbe.process(AProbe.java:84)
at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:125)
at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

 

Release


Jakarta and Kingston.

 

Cause


The cause of this problem is both sensors and patterns enabled at the same time. Either of the one should be used, but not both.

  • There is a DNS probe in discovery which is causing Java exceptions.
  • This probe is for resolving DNS names of IPs.
  • This would get triggered twice, one for SMMP Identity - Multiprobe and once again for Horizontal Pattern probe.
  • When it gets triggered with SMMP Identity - Multiprobe, proper IP Addresses are being sent to DNS probe and it is processing good. No error here.
  • When it gets triggered with Horizontal Pattern probe, "null" parameter is being sent instead of IP Address. And this activity seems to be redundant. 
  • This is because, there are both Probes and Sensors, Patterns enabled for discovery.

Resolution


  • Identify which classification is triggered for the discovery. It should be either "Standard Network Router" or "Standard Network Switch".
  • Open the classifier. (Navigate to Discovery Definition -> CI Classification -> All and search for respective classifier).
  • Under "Triggers Probes" section, you can remove "Horizontal Pattern".
  • Re-run the discovery and it should go good now without errors.

Additional Information


You can contact Customer Support if you have any questions performing the above steps.


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.