Request processing

The following section describes issues with request processing.

Adapter not started

When the adapter is not started, the collaboration is not able to process the service request. The flow ends up as a failed flow and needs to be restarted after having started the adapter

Recommended action: Start the adapter and re-start the failed flow thereafter.

Adapter terminates after a request

The adapter terminates after a request, before indicating a reply for the request. This ends up as a failed flow with the adapter indicating that the status of the request is unknown.

Recommended action: Re-start the failed flow after correcting the problem. This can indicate a duplicate request, which can be handled.

Serialization of application-specific business object

When the serialization of the application-specific business object fails (for example, because there is a data handler problem), the adapter throws an exception and writes an entry into its log file. The flow ends up as a failed flow.

Recommended action: Analyze the messages in the log. Then, correct the adapter bug and restart the adapter. Eventually, restart the failed flow.

Request message cannot be put on the request queue

When the message cannot be put onto the request queue, the adapter terminates. Depending on the adapter's configuration, it can restart automatically. The request flow ends up as a failed flow indicating that there was a queue access problem.

Recommended action: Correct the problem with the WebSphere MQ queue and restart the failed flow.

Copyright IBM Corp. 1997, 2004