ServiceNow engineers have identified that with Discovery when there is a large Vcenter payload and the payload comes back as payload.txt, the input record is not processed and a 'No sensors defined' error message appears.

Steps to Reproduce

  1. Bypass the MID Server max payload size limit (MID Server Property mid.discovery.max_payload_size) so that a payload of >5MB is returned.
  2. Run Discovery against a vCenter that manages a large set of virtual machines.
    The input payload is returned with a payload attachment >5MB. When the sensor tries to process, it returns a 'No sensors defined' error.


In addition to the payload size limit, a preventive measure was introduced in Fuji to prevent reading in large attachments into memory. With the preventative measure, the vCenter sensor is blocked from reading the attached payload.

Until enhancements are made to better handle large attachments, there is no safe method for sensors to continue processing. There are two possible workarounds, but both options put the instance at risk of running out of memory.

Workaround 1:

Increase the system property glide.soapprocessor.large_field_patch_max to a larger value. This allows larger payloads to be written to the payload field on the ecc_queue record, instead of being converted to an attachment.

Workaround 2:

Increase system property com.glide.attachment.max_get_size to a larger value. This allows the vCenter sensor to read in larger payload attachments.

Related Problem: PRB633324

Seen In

Calgary Patch 4
Fuji Patch 1
Fuji Patch 10
Fuji Patch 11
Fuji Patch 12 Hot Fix 1
Fuji Patch 5
Fuji Patch 6
Fuji Patch 9
Fuji Patch 9 Hot Fix 1
Geneva Patch 1
Geneva Patch 3 Hot Fix 2
Geneva Patch 4
Geneva Patch 5
Geneva Patch 6 Hot Fix 2

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-06-07 01:39:26