Error handling

All error messages generated by the connector are stored in a message file. (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 BON_APPRESPONSETIMEOUT is returned when:

Unsubscribed message

The connector delivers a message to the queue specified by the UnsubscribedQueue property if:

Note:
If the UnsubscribedQueue is not defined, unsubscribed messages are discarded.

XML structure errors

The connector delivers a message to the queue specified by the ErrorQueue property if:

Data handler conversion

The connector delivers a message to the queue specified by the ErrorQueue property if:

Errors and the WfMessage document

In addition to responding to standard errors reported by the connector, the connector also responds to errors issued by WebSphere MQ Workflow itself. If an error occurs while the connector is synchronously processing a message issued by the connector, WebSphere MQ Workflow returns a WfMessage containing an Exception element. The text of this element specifies an error message that the connector returns to InterChange Server for failed request operations to the WebSphere MQ Workflow application.

If the connector fails to synchronously process a WfMessage issued by WebSphere MQ Workflow (for any of the aforementioned reasons), the connector attempts to send WebSphere MQ Workflow a response WfMessage containing an Exception element. The connector populates this element with a verbose explanation of the event or events that caused the failure. WebSphere MQ Workflow can use this message to update the state of a failed workflow so that appropriate user intervention can be taken.

Once the connector issues a response to a request that was originally issued by the WebSphere MQ Workflow server, the connector does not wait for an acknowledgement. The connector has no means of receiving an acknowledgement because WebSphere MQ Workflow reports errors only in such cases. To circumvent this problem, the connector specifies in its response message that any error message resulting from the response should be issued to the input queue of the connector. In this fashion, if an error occurs, the connector is eventually notified during pollForEvents. The error is logged, but no further action is taken. Such errors are assumed to be the consequence of response business objects that produce incomplete or incorrect data structures as determined by WebSphere MQ Workflow.

Copyright IBM Corp. 1997, 2003