Callout request errors are often related to the execution
timeout setting, incorrect or corrupted callout messages, or network
failures.
- Execution timeout occurs (no callout message is being
retrieved within the time interval).
Explanation: Possible
reasons include:
- No IMS™ application issues
a callout request and the tpipe does not hold any request.
- The tpipe name that is specified in the alternate client ID field
in the Java™ application does
not match the tpipe name that is used by the IMS application for the callout request.
- The tpipe name that is specified in the alternate
client ID field in the Java application
does not match the tpipe name that is specified in the OTMA destination
descriptor.
- The message processing program (MPP) has not started.
User Action: Either increase the timeout interval
(the executionTimeout property), or verify that the tpipe name matches.
Ensure that the MPP is started.
- IMS Connect fails to process
the callout request and the message is placed in the Dead Letter Queue.
Explanation:
This problem is most likely due to a bad callout message.
User
Action: Fix the callout message in the IMS application.
- IMS Connect fails
to deliver the callout request to the IMS TM
resource adapter.
Explanation This
problem is most likely due to a network failure.
User Action: If
a network failure occurs, you might receive a Java exception. Modify the Java application to catch the exception.
- The IMS TM
resource adapter or
the Java application fails to
process the callout request.
Explanation Possible reasons
include:
- The callout request is corrupted.
- The message is not a callout request, but a regular asynchronous
output message.
User Action: Verify that the callout request is
issued correctly from the IMS application.
Verify that the tpipe name that is specified in the Java application is correct, and that it is
not the name for another queue for a regular asynchronous output message.