MID Server status in instance changes to DOWN after BR "Discovery - Update device started count" attempts to run multiple times. - Known Error

MID Server status in instance changes to DOWN after BR "Discovery - Update device started count" attempts to run multiple times. Description MID Server status in instance changes to DOWN after BR "Discovery - Update device started count" attempts to run multiple times.

Steps to Reproduce

Upgrade MID Server to Quebec Patch 0 Hotfix 4 After few minutes MID server status in instance changes to Down. In MID Server Agent log we see error executing business rule 'Discovery - Update device started count' triggered multiple times

StartupSequencer WARNING *** WARNING *** MIDRemoteGlideRecord.insert failed, retrying in 10 seconds StartupSequencer WARNING *** WARNING *** Method failed: (https:// .service-now.com/ecc_queue.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 500 Internal Server Error with code: 500 StartupSequencer WARNING *** WARNING *** Error executing business rule 'Discovery - Update device started count' StartupSequencer WARNING *** WARNING *** RemoteGlideRecord failed to send data to https:// .service-now.com/ with (Error executing business rule 'Discovery - Update device started count')

StartupSequencer DEBUG: Event: RGRPerfMetricEvent StartupSequencer WARNING *** WARNING *** MIDRemoteGlideRecord.insert failed, retrying in 15 seconds StartupSequencer WARNING *** WARNING *** Method failed: (https:// .service-now.com/ecc_queue.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 500 Internal Server Error with code: 500 StartupSequencer WARNING *** WARNING *** Error executing business rule 'Discovery - Update device started count' StartupSequencer WARNING *** WARNING *** RemoteGlideRecord failed to send data to https:// .service-now.com/ with (Error executing business rule 'Discovery - Update device started count')

StartupSequencer DEBUG: Event: RGRPerfMetricEvent StartupSequencer WARNING *** WARNING *** MIDRemoteGlideRecord.insert failed, retrying in 22 seconds StartupSequencer WARNING *** WARNING *** Method failed: (https:// .service-now.com/ecc_queue.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 500 Internal Server Error with code: 500 StartupSequencer WARNING *** WARNING *** Error executing business rule 'Discovery - Update device started count' StartupSequencer WARNING *** WARNING *** RemoteGlideRecord failed to send data to https:// .service-now.com/ with (Error executing business rule 'Discovery - Update device started count')

StartupSequencer DEBUG: Event: RGRPerfMetricEvent StartupSequencer WARNING *** WARNING *** MIDRemoteGlideRecord.insert failed, retrying in 33 seconds StartupSequencer WARNING *** WARNING *** Method failed: (https:// .service-now.com/ecc_queue.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 500 Internal Server Error with code: 500 StartupSequencer WARNING *** WARNING *** Error executing business rule 'Discovery - Update device started count' StartupSequencer WARNING *** WARNING *** RemoteGlideRecord failed to send data to https:// .service-now.com/ with (Error executing business rule 'Discovery - Update device started count')

StartupSequencer WARNING *** WARNING *** Method failed: (https:// .service-now.com/ecc_queue.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 500 Internal Server Error with code: 500 StartupSequencer WARNING *** WARNING *** Error executing business rule 'Discovery - Update device started count' StartupSequencer WARNING *** WARNING *** RemoteGlideRecord failed to send data to https:// .service-now.com/ with (Error executing business rule 'Discovery - Update device started count') StartupSequencer DEBUG: Event: RGRPerfMetricEvent StartupSequencer WARNING *** WARNING *** MIDRemoteGlideRecord.insert failed, retrying in 120 seconds

THEN THE MID SERVER STOPPED

WrapperListener_stop_runner Running under Java version: 11.0.8-sncmid1, java PID: 10268, args: stop WrapperListener_stop_runner JVM default socket factory: class sun.security.ssl.SSLSocketFactoryImpl WrapperListener_stop_runner Stopping MID server

Workaround The MID server does actually enqueue output records of topic "LDAPListenProbe" when starting LDAP server listeners during MID startup. These records do not have a payload. The BR being referenced here extracts the payload for parsing, and it is trying to index an undefined array in this case.

As a workaround for this, in the business rule execution conditions add the following condition: 'current.topic != 'LDAPListenProbe'. This should exclude only those records from being processed with the business rule.