MQ middleware channel status STATUS (RETRYING) problem analysis and solution This problem is generally sent at the sending end. After we issue the command to start the channel, the channel enters the binding state. If the network connection is smooth and the channel is defined correctly, it enters In the normal running state, if the following problems occur, the channel enters the retrying state. Check Channel Status exemplary $ the runmqsc the QMgrName DIS CHS (C) AMQ8417:. Details Display the Status Channel the CHANNEL (C) XMITQ The (the QX) the CONNAME (xxx.xxx.xxx.xxx (1416)) the CURRENT CHLTYPE The (the SDR) the STATUS (RETRYING) Cause There may be the following: 1. There is a problem with the network connection 2. The channel definition is incorrect 3. The message sequence numbers at both ends of the channel do not match 4. The CONNAME (HostName (PortNumber)) in the channel definition uses the host name but There is no definition in the hosts file 5. The receiver cannot be connected 6. The receiver does not start monitoring 7. The port of the receiver is occupied (for example, the port is occupied by other queue managers) Solution A. There is a problem with the network connection Check the channel definition including the network is unavailable, you can use the telnet port to test the connection B. The message sequence numbers at both ends of the channel do not match. For details, please refer to this article: Websphere MQ Message Sequence Number Detailed Explanation C. The channel definition is incorrect. Check the channel configuration. Check method: $ runmqsc QMgrName dis chl (ChannelName) D. The CONNAME (HostName (PortNumber)) in the channel definition uses the host name but it is not defined in the hosts file. Check the channel definition. Check method: $ runmqsc QMgrName dis chl (ChannelName) Check whether the CONNAME uses the host name, if it is used , Please check if there is a definition in the / etc / hosts file. E. The receiver cannot be connected and F. The receiver has not started the monitoring check method: The test channel command PING in MQSC has the following format: The $ runmqsc QMgrName PING CHANNEL (channel_name) [DATALEN (16 | integer)] where DATALEN represents PING data The packet size can be from 16 bytes to 32,768 bytes. The PING command can check whether the other party's queue manager or port listener is started, and can also check whether the other party's channel definition is correct. However, the general state of the channel is not checked. In other words, PING CHANNEL only checks whether the channel can be connected, not whether it is currently connected. G. The receiving port occupies the corresponding queue manager at the receiving end to stop listening, and then check whether the port is still listening: $ netstat -an | grep port number