IB client (outbound) thread: Error conditions
When an error happens, Intelligent Broker populates the IBStatus
of the ibmime
message with the values that are listed in this topic. It also includes a detailed
error description in the ibmime message body.
The Intelligent Broker log files also have detailed information about the error:
-
APP_REJECT
An exception could happen which is not an application-level error according to the business logic. For example, the remote service finds that the requested resource cannot be granted. A system or network level error could happen, so the remote endpoint is inaccessible by the local Intelligent Broker. For example, the remote endpoint URL that is given in the Intelligent Broker client thread properties is not a valid URL. The
IBStatus
that is returned by the local Intelligent Broker then has the value of APP_REJECT with a subcodea /
.For example, APP_REJECT/HXML_47.
The message body contains a detailed error description.
Common sub-codes APP_REJECT include:
- IB_00: Reason not known. The error description might contain more detail.
- IB_01: Indicates that the remote endpoint is not running or otherwise not accessible. This indicates that it is not permitted or the resource is not found on the endpoint.
- IB_02: The remote host indicated in the endpoint URL does not exist.
- IB_03: The message being sent is not well-formed XML.
- IB_04: The message being sent does not have a valid soap Envelope.
- IB_05: Indicates the remote endpoint has not sent back a response in a preset period of time. This could result if the IP does not respond at all or is merely taking more time to process than permitted.
- IB_06: The outbound message has an attachment with no content type header.
- IB_07: A non-integer was passed in the IBSoapSendTimeout header.
- IB_08: The destination is missing protocol, most likely an invalid site/thread or IBEndpointURL header is missing http:// part.
COMMIT_ERR
Certain errors are not caused by system or network anomalies, in which case the
IBStatus
in the reply contains COMMIT_ERR. For example, There are software problems or otherwise unknown reasons.An outbound thread making a request/response web service invocation can get back APP_RESP, APP_REJECT, or COMMIT_ERR.
A one-way web service invocation can get back APP_ACCEPT, APP_REJECT, or COMMIT_ERR.
Among all of these replies, only the APP_RESP reply has a meaningful content associated with the rest of the ibmime structure.