Zabbix Event Connector Failing with "ERROR EXECUTING REQUEST: null" error.Descriptionit is observed that the Zabbix Event Connector Failing with the below error when a Test connection is performed. EVENTS-------------------------------------------------------------ERROR EXECUTING REQUEST: nullCauseThe error on UI shows as "ERROR EXECUTING REQUEST: null" error. But when we enable the Mid Debug Logs and execute test connection, we see Out of Memory error. Below is the log context 2021-01-27 06:20:59 (379) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 *** Script: **** ZABBIXJS ERROR: ERROR EXECUTING REQUEST: null2021-01-27 06:20:59 (379) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 *** Script: **** ZABBIXJS ERROR: JavaException: java.lang.OutOfMemoryError: Java heap space2021-01-27 06:20:59 (379) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 DEBUG: Event: GenericScalarMetricEvent2021-01-27 06:20:59 (379) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 Slow execution (79226ms) of script: probe:ZabbixJS2021-01-27 06:20:59 (379) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 Status: FAILURE2021-01-27 06:20:59 (394) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 DEBUG: Event: GenericScalarMetricEvent2021-01-27 06:20:59 (394) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 DEBUG: Event: CheckSessionCanceledEvent, correlator: , sysID: a99c68d81bcaa010be24eca13d4bcbc1, canceled: false2021-01-27 06:20:59 (394) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 Enqueuing: D:\ServiceNow\DevMid-01\agent\work\monitors\ECCSender\output_0\ecc_queue.a99c68d81bcaa010be24eca13d4bcbc1.xml2021-01-27 06:20:59 (394) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 DEBUG: Event: GenericCounterMetricEvent2021-01-27 06:20:59 (394) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 DEBUG: ** enqueued D:\ServiceNow\DevMid-01\agent\work\monitors\ECCSender\output_0\ecc_queue.a99c68d81bcaa010be24eca13d4bcbc1.xml2021-01-27 06:20:59 (394) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 DEBUG: Event: MessageProcessedEvent, sysID: a99c68d81bcaa010be24eca13d4bcbc12021-01-27 06:20:59 (394) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 DEBUG: Event: SendMessageEvent, message: ConnectorProbe Zabbix Prod_Inflow 2021-01-27 06:20:59 (394) Worker-Interactive:ConnectorProbe-a99c68d81bcaa010be24eca13d4bcbc1 Worker completed: ConnectorProbe source: Zabbix Prod_Inflow time: 0:01:20.836ResolutionThis error is caused because the incoming payload has huge data and the mid server is unable to handle it. In order to resolve this issue, we actions can be taken: We need to make sure that the MID Servers used by the Zabbix connector is used only for this purpose and is installed on a host machine where no other MID Server is installed for other purposes.The MID Server should be provided with a minimum of total 12GB memory(8GB for JVM + 4 GB for OS).8 GB JVM memory can be given to the MID Server by editing the following line in the wrapper-override.conf file. # OPTIONAL: Maximum Java Heap Size (in MB)wrapper.java.maxmemory=8192 https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/mid-server/reference/r_MIDServerSystemRequirements.html#d1019049e449 Additional InformationIn the current use case, the mid server host was having 16 GB RAM, out of which we have allocated 8 GB for the mid server. No more errors, we are now successfully able to get events from Zabbix.Another thing to make sure of is that the "days_from" parameter of the connector is set to 1 day and not 7 days - this will try to bring the data for 1 day.The protocol used for the connection should be HTTPS, in one of the cases we observed that if HTTP is used, then the connector shows an "Unknown Host" error.