Error handling

All error messages generated by the connector are stored in a message file named JMSConnector.txt. (The name of the file is determined by the LogFileName standard connector configuration property.) Each error has an error number followed by the error message:

Message number
Message text

The connector handles specific errors as described in the following sections.

Application timeout

The error message APP_RESPONSETIMEOUT is returned when:

Unsubscribed business object

If the connector retrieves a message that is associated with an unsubscribed business object, or if a NO_SUBSCRIPTION_FOUND code is returned by the gotApplEvent() method, the connector delivers a message to the queue specified by the UnsubscribedDestination property.

Note:
If the UnsubscribedDestination is not defined, unsubscribed messages will be discarded.

Connector not active

When the gotApplEvent() method returns a CONNECTOR_NOT_ACTIVE code, the pollForEvents() method returns an APP_RESPONSE_TIMEOUT code and the event remains in the InProgress Destination, if specified.

Data handler conversion

If the data handler fails to convert a message to a business object, or if a processing error occurs that is specific to the business object (as opposed to the JMS provider), the message is delivered to the queue specified by ErrorDestination. If the ErrorDestination is not defined, messages that cannot be processed due to errors are discarded.

If the data handler fails to convert a business object to a message, FAIL is returned.

Copyright IBM Corp. 1997, 2004