Discovery may hang if the classify input is larger than 512kb - Known Error

Discovery may hang if the classify input is larger than 512kb Description A discovery will hang if the following conditions match: 1. The schedule has several IP Address for the same device 2. Classify input payload is larger than 512kb 3. Duplicate IP Detection is enabled

Steps to Reproduce

Have a device with multiple IP addresses. Enable duplicate IP detection. Create a discovery schedule and an IP range for all IP addresses for the device in step 1. Configure the system property glide.soapprocessor.large_field_patch_max to be smaller than the classify payload size (in bytes). Run a scan on the schedule. Observe that the revisit does not occur. ECC queue records for duplicate IPs are stuck in the 'Ready' state and the discovery status is stuck in the 'Active' state.

Workaround 1. For the Classify Input that is stuck in 'Ready' state, get the IP Address (source field)

2. Goto the 'discovery_device_duplicate_ips' table and search for the same IP Address and same Discovery status

3. Show matching on the CI and remove filter on IP Address. This will show all IP Addresses for the same device being scanned in the same Discovery Status

4. Pick an IP Address from the list above whose state is not 'Duplicate IP' or 'Skip IP'

5. Goto the discovery status and search for ECC Queue input for the IP Address above

6. Save the payload to see how large it is.

7. Adjust the System Property "glide.soapprocessor.large_field_patch_max" to be slightly larger than the above payload size (in bytes). NOTE: do not change this value to a very large number. Preferably not more than a couple of MBs.