Unexpected messages are received when using distributed queues

If your application uses distributed queues, consider the following points:

• Has distributed queuing been correctly installed on both the sending and receiving systems?

• Are the links available between the two systems?

  Check that both systems are available, and connected to WebSphere MQ for iSeries. Check that the connection between the two systems is active.

• Is triggering set on in the sending system?

• Is the message you are waiting for a reply message from a remote system?

  Check that triggering is activated in the remote system.

• Is the queue already full?

  This could mean that an application was unable to put the required message on to the queue. If this is so, check if the message has been put onto the undelivered-message queue.

  The dead-letter queue message header (dead-letter header structure) contains a reason or feedback code explaining why the message could not be put on to the target queue. See the WebSphere MQ Application Programming Reference or the WebSphere MQ for iSeries Application Programming Reference (ILE RPG), as appropriate, for information about the dead-letter header structure.

• Is there a mismatch between the sending and receiving queue managers?

  For example, the message length could be longer than the receiving queue manager can handle.

• Are the channel definitions of the sending and receiving channels compatible?

  For example, a mismatch in sequence number wrap stops the distributed queuing component. See WebSphere MQ Intercommunication for more information about distributed queuing.