Troubleshooting and getting help

VCO Discovery fails with Java Exception

If the VCO discovery fails with Java Exception and below message appears in ESM logs:

NV_MESSAGE-*-NV_GENERIC-MSG ERR : [Thread-3 DiscoveryManager]:Null message received from kafka. It may be due to not having any data with in 100 seconds.

[June 18, 2019 4:26:36 AM EDT +019ms] t@219129600 Discovery #4
NV_MESSAGE-*-NV_GENERIC-MSG ERR : [Thread-3 VcoDiscovery]:Exception in Discovery through DCF collector

[June 18, 2019 4:26:36 AM EDT +022ms] t@1259902720 platform
MAIN_MSG-*-STDFD_ERR-stderr: java.lang.Exception: Error while receiving data from the kafka topic

[June 18, 2019 4:26:36 AM EDT +022ms] t@1259902720 platform
MAIN_MSG-*-STDFD_ERR-stderr: at com.emc.asd.stream.discovery.vco.DiscoveryManager.startDiscovery(DiscoveryManager.java:137)
at com.emc.asd.stream.discovery.vco.VcoDiscovery.invoke(VcoDiscovery.java:170)
at com.smarts.java_probe.ProbeRunner.invoke(ProbeRunner.java:69)

Workaround:

Below parameter need to be set if there is a network latency and ESM is unable to read data from Kafka within default value of 100 seconds. Due to which VCO is not discovered.

MessagePollTimeoutPeriodInSeconds-<kafka_IP> 1200" .

Getting help

VMware support, product, and licensing information can be obtained as follows.

Product information - For documentation, release notes, software updates, or for information about products, go to VMware Online Support at: