Common error messages

Failed to get message text

The JMS transport module failed to get the text from the JMS message that it received.

There was a problem with the format of the message received from the JMS.

Unsupported message type

The JMS has received a message that is not a text message.

Only messages in text format are supported.

No transformer defined for name name

The gateway is trying to find the correct transformer to use to transform an event, but the message ID for that transformer is not present in the transformers.xml file.

Add a transformer to the transformers.xml file that corresponds to the message ID.

No endpoint defined for name name

The gateway is trying to find the correct endpoint to send a message to, but the transformer in the transformers.xml file for this message does not specify an endpoint.

Specify an endpoint for the transformer that corresponds to this message.

No transformer defined for endpoint endpoint

The probe has received an event from an endpoint for which there is no transformer in the transformers.xml file.

Add a transformer to the transformers.xml file for this endpoint.

Invalid entry in transformer definition file - duplicate endpoint endpoint in southbound transformer entry

Two southbound transformers in the transformers.xml file have been specified with the same endpoint.

You can only create one southbound transformer for each endpoint. Remove one of the transformers from the transformers.xml file.

Invalid entry in transformer definition file - duplicate name name in northbound transformer entry

Two northbound transformers in the transformers.xml file have been specified with the same name.

You cannot create two northbound transformers with the same name. Rename one of the transformers.

Invalid transformer type type specified in transformers file

A transformer in the transformers.xml file specifies a transformer type that is not supported.

The message type should either be northbound or southbound. Update the transformer in the transformers.xml file.

Property type type does not exist

The type specified for a property definition with a transformer is not a Java™ object.

Correct the transformer in the transformers.xml file by specifying a valid Java object name, for example, java.lang.String.

Invalid property name propName in transformer name

The name specified for a property definition with a transformer is not valid.

Correct the transformer in the transformers.xml file by specifying a valid name. This should be XSLT file name.

Method method_name in class transformerClass has thrown an exception

The method specified in the transformer definition file has failed.

Use the information in the message to diagnose the problem.

Failed to read transformer definition file

The transformer module failed to read the transformer definition file (transformers.xml).

Check that the file is specified correctly and that the permissions on the transformers.xml file are set correctly.

Unknown property

A transformer in the transformers.xml file contained a property that is not recognized.

Update the transformer in the transformers.xml file.

Failed to transform message

The transformer module could not transform an XML event.

There may be a problem with the XLST file. Try testing it using the transformer validation tool.

Failed to read XSLT file

The transformer module failed to read an XSLT file specified within the transformer definition file.

Check that the file is specified correctly and that the permissions on the .xsl file are set correctly.

Invalid transformer class name found

A transformer in the transformers.xml file contains an invalid transformer class name.

Check that you have specified the transformer class correctly in the transformers.xml file.

Failed to close file

Failed to find file

The named file was not found.

Check that the name of the file has been specified correctly in the properties file.

Stream file filename is not a stream capture file

The file identified is not a stream capture file and cannot be used by the transport module.

Specify an alternative file name in the transport properties file.

I/O exception whilst opening file

The transport module could not open the file specified.

Check the permissions on the file indicated.

Failed to read object from file

The probe failed to read the stream capture file.

Try recreating the stream capture file and running it through the probe again.

Error in stream capture file

The stream capture file identified contains an error.

Try recreating the stream capture file and running it through the probe again.

Failed to find initial context

The class name in the transport properties file is incorrect.

Check the setting of the initialContextFactory property.

Failed to create subscriber for topic: topicName

The transport module failed to subscribe to a topic with the JMS.

Use the information in the message to diagnose the problem.

JNDI lookup for topic: topicName

Failed to find topicName in JNDI

The transport module could not find one of the topics specified in the JNDI.

Check that the topic has been specified correctly in the transport file.

Failed to start JMS subscriber

The transport module failed to start the JMS subscriber.

Use the information in the message to diagnose the problem.

Failed to send message

The transport module failed to send a message to the endpoint specified in the transformer.

Use the information in the message to diagnose the problem.

Failed to find topicName in JNDI

The transport module cannot find one of the topics in the JNDI.

Check that the topic has been specified correctly in the transport file.

Failed to close topic connection

The transport module failed to close a topic connection within JMS.

Use the information in the message to diagnose the problem.

Invalid property propName

The transport properties file contains a property that is not supported.

Update the transport properties file.

Invalid transport class name found

The transportModule property of the transport file contains an invalid class name.

Change the value of the transportModule property to a class that exists in the jar file.

Failed to load properties file

The transport module could not read the transport properties file.

Check that the properties file exists and that the permissions are set correctly.

Invalid property propName in file transportFile does not exist in transport class transportClass

The transport file contained a property that is not supported by the transport module.

Update the transport properties file. For a description of the properties that the transport files supports, see Configuring the transport properties files.

Method methodName in class transportClass has thrown an exception

The method specified in the transport file has failed.

Use the information in the message to diagnose the problem.

key + " contains non-existent environment variable value

A value in the transport properties file or in the transformer file contains an environment variable which does not exist.

Set the environment variable specified to an appropriate value.

Failed to create JMS connection

The transport module failed to create a connection to the JMS.

Check that you have specified the parameters correctly in the transport properties file.

Failed to parse message

The probe failed to parse the message. This could be caused by an invalid character such as a non-printable character in the raw data.

Verify that the inbound data is in the correct format and structure.

Timed out waiting for response

The probe sent an HTTP request but the response did not arrive within the timeout period. This applies to the REST/Websocket transport.

Check the URI used for each request. Check that the target received the HTTP request from the probe and responded within the specified timeout period.