Error messages

Error messages provide information about problems that occur while running the probe. You can use the information that they contain to resolve such problems.

The following table describes the error messages specific to this probe. For information about generic error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 1. Error messages




Failed to startup probe

The probe failed to start, probably due to an invalid combination of properties set in the message_bus.props file.

Check the values set for the Host, Port Username, and Password properties.

Failed to transform

The probe is unable to transform the XML into name-value pairs.

Check the entries in the transformer file. Then test the XSLT file created for the event source.

Failed to parse message

The probe could not parse the event data.

Check the format of the event generated by the XML event source.

Failed to record data into backup file

The probe could not write record data into the backup file.

Check that the backup file is specified correctly by the DataBackupFile property in the message_bus.props file and that the file has the appropriate permissions set.

Failed to start Transport module for connection

The transport module failed to start.

Check the value set for the TransportType property and the details specified in the TransportFile.

Failed to subscribe Transport module to the interface

The transport module failed to subscribe to the event source.

Check the details specified in the TransportFile.

Failed to get active alarms during resync

The probe failed to received active alarms during resynchronization with the event source.

Check the details specified in the TransportFile.

Exception caught in WebSocketClientHandler: Queue full

Note: This error message only applies when the Probe for Message Bus runs with the WebSocket transport.

The WebSocket transport event queue has reached its limit and has started to discard events. This usually occurs in a flooding scenario or if the event processing is slow or blocked.

Verify that no other error occurred in the probe log or ObjectServer logs that could potentially slow down or block the probe event processing.

Verify that the probe is not under a flood or denial-of-service attack.