This topic provides a set of specific tips to help you troubleshoot problems with WebSphere MQ link.
Look for messages CWSIC3011E, CWSIC3015E.
Look for messages CWSIC3018E, CWSIC3113E, CWSIC3114E, CWSIC3236E.
Look for message CWSIC3010E.
Look for message CWSIC3065E.
Verify that the WebSphere MQ link sender channel channel is started and in running state.
Verify that the sender channel in WebSphere MQ network is started and in running state.
Look for messages CWSIC3096I, CWSIC3098I, CWSIC3200E, CWSIC3209E.
Check the exception destination(s) and the dead letter queue. It is possible that the target destination has not been defined, or is full in which case, determine why messages are not being processed from the target destination.
Look for message CWSIP0291W.
Determine why messages are not being processed from the target destination.
Check the persistence of messages being generated by your application(s).
Look for message CWSIC3080E.
If a WebSphere MQ link sender channel does not have any messages to deliver, it waits for its specified disconnect interval before timing out. If the application server is shut down while a WebSphere MQ link sender channel is in a wait state, the application server waits for the WebSphere MQ link sender channel to timeout before shutting down. A long disconnect interval might delay the server shutdown.
To reduce possible delays during application server shutdown, you can specify a smaller value for the disconnect interval. Note that a discount interval of 0 indicates an indefinite wait. For more information about setting the disconnect interval for a WebSphere MQ link sender channel, see Modifying a WebSphere MQ link sender channel.