ProbeWatch messages

During normal operations, the probe generates ProbeWatch messages and sends them to the ObjectServer. These messages tell the ObjectServer how the probe is running.

The following table describes the ProbeWatch messages that the probe generates. For information about generic Netcool/OMNIbus ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 1. ProbeWatch messages
ProbeWatch message	Description	Triggers/causes
`Could not find JNDI context topic topic_name`	There was an error when the probe attempted to connect to the NFM-P server.	The JMS did not start properly on the NFM-P server.
`Failed to establish HTTP connection for resync`	The probe has failed to establish an HTTP connection to the NFM-P server.	The probe failed to connect to the port specified by the HTTPPort property.
`Going Down`	The probe is shutting down.	The probe is shutting down after performing the shutdown routine.
`JNDI API lookup failed`	There was an error when the probe attempted to connect to the NFM-P server.	The JMS did not start properly on the NFM-P server.
`Running ...`	The probe is running normally.	The probe has just been started up.
`Unsupported Java class version error`	An unsupported Java class version exception occurred while the probe was initializing the JMS connection to the EMS.	The server is running a version of Java other than 1.8.
`xmlFilterChangeEvent received, advanced filtering registration is successful`	The probe successfully completed an advanced filtering registration.	The probe received an `xmlFilterChangeEvent` from the NFM-P server.
`Failed to register advanced filtering`	This indicates that the advanced filtering failed to register.	The NFM-P server returned an exception status of `1`. Check the advanced XML filter specified by the AdvancedFilterConfigFile property and retry running the probe.
`Some classes are missing from the CLASSPATH. Exiting.`	The probe could not find the necessary class during connection.	Check that you have copied the necessary JAR files from the NFM-P server into the Netcool/OMNIbus environment.
`Unable to parse event due to IOException`	The probe could not parse events due to an `IO` exception. This may cause event loss.	Contact IBM support for assistance.
`Unable to parse event due to SAX Parser exception`	The probe could not parse events due to a `SaxParser` exception. This may cause event loss.	Contact IBM support for assistance.
`START SYNCHRONIZATION`	A resynchronization operation started.	The probe started receiving active alarms from EMS.
`STOP SYNCHRONIZATION`	A resynchronization operation completed.	The probe stopped receiving active alarms from EMS.
`Connecting new primary NFM-P server`	This ProbeWatch message is used to notify user about the probe is setting up connection to new primary NFM-P server after detected NFM-P activity switch in redundant NFM-P system.
`Connected to primary NFM-P server`	The probe is connected to primary NFM-P server.