All error messages generated by the connector are stored in a message file named MQSIV2Connector.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.
The error message ABON_APPRESPONSETIMEOUT is returned when:
The connector delivers a message to the queue specified by the UnsubscribedQueue property if:
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 queue.
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 ErrorQueue. If the ErrorQueue is not defined, messages that cannot be processed due to errors will be discarded.
If the data handler fails to convert a business object to a message, BON_FAIL is returned.
If a JMS property cannot be read from or written to a message, the connector logs an error and the request or event fails. If a you do not specify a ReplyToQueue or it cannot be accessed, the connector logs an error and the request fails. If a CorrelationID is invalid or cannot be set, the connector logs an error and the request fails.
In all cases, the message logged is from the connector message file.
When retrieving a message, the connector normally matches the input format to one specific business object and verb combination. The connector then passes the business object name and the contents of the message to the data handler. This allows the data handler to verify that the message contents correspond to the business object that the user expects.
If, however, the same input format is defined for more than one business object, the connector will be unable to determine which business object the data represents before passing it to the data handler. In such cases, the connector passes the message contents only to the data handler and then looks up conversion properties based on the business object that is generated. Accordingly, the data handler must determine the business object based on the message content alone.
If the verb on the generated business object is not set, the connector searches for conversion properties defined for this business object with any verb. If only one set of conversion properties is found, the connector assigns the specified verb. If more properties are found, the connector fails the message because it is unable to distinguish among the verbs.