AMQ9208

Question

版本情況如下：
Name:        WebSphere MQ
Version:     530.13  CSD13
CMVC level:  p530-13-L061205
BuildType:   IKAP - (Production)

MQ錯誤訊息如下：

重啟前有如下錯誤：
12/08/09  11:40:46
AMQ9208: Error on receive from host 10.80.30.87.
EXPLANATION:
An error occurred receiving data from 10.80.30.87 over TCP/IP. This may be due
to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 73 (X'49'). Record these values
and tell the systems administrator.
----- amqccita.c : 2743 -------------------------------------------------------

重啟MQ還會有同樣的錯誤：

12/08/09  13:11:44
AMQ9208: Error on receive from host 10.80.30.87.
EXPLANATION:
An error occurred receiving data from 10.80.30.87 over TCP/IP. This may be due
to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 73 (X'49'). Record these values
and tell the systems administrator.
----- amqccita.c : 2743 -------------------------------------------------------
12/08/09  13:12:43
AMQ9411: Repository manager ended normally.
EXPLANATION:
The repository manager ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
12/08/09  13:12:44
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrmssa.c : 2120 -------------------------------------------------------
12/08/09  13:12:44
AMQ9001: Channel 'TO_QM_COPTI2' ended normally.
EXPLANATION:
Channel 'TO_QM_COPTI2' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
12/08/09  13:12:44
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrimna.c : 859 --------------------------------------------------------
12/08/09  13:12:44
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrmssa.c : 2120 -------------------------------------------------------
12/08/09  13:12:44
AMQ9001: Channel 'TO_QM_COPTI1' ended normally.
EXPLANATION:
Channel 'TO_QM_COPTI1' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
12/08/09  13:12:55
AMQ8004: WebSphere MQ queue manager 'QM_CGW1' ended.
EXPLANATION:
WebSphere MQ queue manager 'QM_CGW1' ended.
ACTION:
None.
-------------------------------------------------------------------------------
12/08/09  13:16:29
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrmssa.c : 2120 -------------------------------------------------------
12/08/09  13:16:38
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'QM_CGW1' failed with reason code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 427 --------------------------------------------------------
12/08/09  13:16:38
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'QM_CGW1' failed with reason code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 427 --------------------------------------------------------
12/08/09  13:16:38
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'CHN_OPTI' ended abnormally.
ACTION:
Look at previous error messages for channel program 'CHN_OPTI' in the error
files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
12/08/09  13:16:38
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'CHN_OPTI' ended abnormally.
ACTION:
Look at previous error messages for channel program 'CHN_OPTI' in the error
files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
12/08/09  13:16:59
AMQ8003: WebSphere MQ queue manager 'QM_CGW1' started.
EXPLANATION:
WebSphere MQ queue manager 'QM_CGW1' started.
ACTION:
None.
-------------------------------------------------------------------------------
12/08/09  13:17:00
AMQ9410: Repository manager started
EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
12/08/09  13:17:00
AMQ8024: WebSphere MQ channel initiator started.
EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
-------------------------------------------------------------------------------
12/08/09  13:18:03
AMQ9208: Error on receive from host 10.80.30.94.
EXPLANATION:
An error occurred receiving data from 10.80.30.94 over TCP/IP. This may be due
to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 73 (X'49'). Record these values
and tell the systems administrator.
----- amqccita.c : 2743 -------------------------------------------------------
12/08/09  13:18:24
AMQ9208: Error on receive from host 10.80.30.94.
EXPLANATION:
An error occurred receiving data from 10.80.30.94 over TCP/IP. This may be due
to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 73 (X'49'). Record these values
and tell the systems administrator.
----- amqccita.c : 2743 -------------------------------------------------------
AMQ9208: Error on receive from host 10.80.30.94.
EXPLANATION:
An error occurred receiving data from 10.80.30.94 over TCP/IP. This may be due
to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 73 (X'49'). Record these values
and tell the systems administrator.

請大俠們幫忙，若要提供別的訊息再告訴我，謝謝！

Answer 1

@dingjiahappy
也就是查查防火墙，以及网络配置上有什么问题。

http://www-01.ibm.com/support/docview.wss?uid=swg21190281

Many times this issue can be seen in firewall environment and has been seen with network DNS problems and/or network config problems. One of the most common is when a passive device (router, switch, hub, etc.) is in between the client & the server. If the port on the passive device is set to Auto-Negotiate, it will automatically defer to the active device (the NIC in the client) to set the connection speed. If the NIC is also set to Auto-Negotiate (default in most OS's) this often causes excessive delays and interruptions in connectivity. This is because the NIC is looking to the network appliance to set the connection speed and vice-versa, it takes some time before the network device will find a suitable connection speed (not always optimal, just suitable) and begin data transfer. This repeats every time a data packet is sent across the network. While the negotiating period is relatively short by human standards (usually in the nanosecond range) it adds up over time when trying to send a large amount of data at a high speed and causes the connection to be broken. The best work around for that is to hard code both the NIC and the network port for a specific setting. This is usually 100Mb Full Duplex for a standard CAT-5 copper connection, although older equipment may require reconfiguration of 10/100 NICs to allow for that speed.

Answer 2

若要提供別的訊息再告訴我，謝謝

Answer 3

你用的通道类型是请求-发送吧，查看下你的队列管理器和对端队列管理器的监听是否都建立并启动了