如何从 Windows 连接远程 Q 管理器（在 docker 上）？答案

【问题标题】：How to connect Remote Q manager(on docker) from windows?如何从 Windows 连接远程 Q 管理器（在 docker 上）？
【发布时间】：2020-05-08 04:02:31
【问题描述】：

我在 docker 容器上有一个 MQ 环境。我在以下链接的帮助下创建了队列管理器 QM_TEST： https://www-01.ibm.com/support/docview.wss?uid=swg21623113

我无法从 Windows 的 MQ 资源管理器连接队列管理器。连接 Q 管理器时出现通道跟随错误。

无法与队列管理器建立连接。无法识别通道名称 (AMQ4871) 严重性：10（警告）说明: 连接到队列管理器的尝试失败。队列管理器无法识别通道名称。 Snap1 Snap2 Snap3 Snap4 Snap5

AMQ5052I: The queue manager task 'QPUBSUB-CTRLR' has started.

EXPLANATION:
The publish/subscribe utility task manager has started the QPUBSUB-CTRLR task.
This task has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.30) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.722Z)
                    ArithInsert2(1)
                    CommentInsert1(TOPIC-TREE)

AMQ5051I: The queue manager task 'TOPIC-TREE' has started.

EXPLANATION:
The critical utility task manager has started the TOPIC-TREE task. This task
has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.34) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.722Z)
                    ArithInsert2(1)
                    CommentInsert1(MULTICAST)

AMQ5051I: The queue manager task 'MULTICAST' has started.

EXPLANATION:
The critical utility task manager has started the MULTICAST task. This task has
now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.31) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.722Z)
                    ArithInsert2(1)
                    CommentInsert1(RESOURCE_MONITOR)

AMQ5051I: The queue manager task 'RESOURCE_MONITOR' has started.

EXPLANATION:
The critical utility task manager has started the RESOURCE_MONITOR task. This
task has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.33) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.723Z)
                    ArithInsert2(1)
                    CommentInsert1(PRESERVED-Q)

AMQ5051I: The queue manager task 'PRESERVED-Q' has started.

EXPLANATION:
The critical utility task manager has started the PRESERVED-Q task. This task
has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62299.5) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.723Z)
                    ArithInsert2(1)
                    CommentInsert1(QPUBSUB-QUEUE-NLCACHE)

AMQ5052I: The queue manager task 'QPUBSUB-QUEUE-NLCACHE' has started.

EXPLANATION:
The publish/subscribe utility task manager has started the
QPUBSUB-QUEUE-NLCACHE task. This task has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62299.7) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.724Z)
                    ArithInsert2(1)
                    CommentInsert1(PUBSUB-DAEMON)

AMQ5052I: The queue manager task 'PUBSUB-DAEMON' has started.

EXPLANATION:
The publish/subscribe utility task manager has started the PUBSUB-DAEMON task.
This task has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62299.7) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.724Z)
                    CommentInsert1(IBM MQ Distributed Pub/Sub Controller)

AMQ5975I: 'IBM MQ Distributed Pub/Sub Controller' has started.

EXPLANATION:
'IBM MQ Distributed Pub/Sub Controller' has started.
ACTION:
None.
----- cmqxzmup.c : 3951 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.32) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.726Z)
                    ArithInsert2(1)
                    CommentInsert1(Q-DELETION)

AMQ5051I: The queue manager task 'Q-DELETION' has started.

EXPLANATION:
The critical utility task manager has started the Q-DELETION task. This task
has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62299.8) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.731Z)
                    CommentInsert1(IBM MQ Distributed Pub/Sub Fan Out Task)

AMQ5975I: 'IBM MQ Distributed Pub/Sub Fan Out Task' has started.

EXPLANATION:
'IBM MQ Distributed Pub/Sub Fan Out Task' has started.
ACTION:
None.
----- cmqxzmup.c : 383 --------------------------------------------------------
06/14/19 05:21:34 - Process(62299.9) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.733Z)
                    CommentInsert1(IBM MQ Distributed Pub/Sub Command Task)

AMQ5975I: 'IBM MQ Distributed Pub/Sub Command Task' has started.

EXPLANATION:
'IBM MQ Distributed Pub/Sub Command Task' has started.
ACTION:
None.
----- cmqxzmup.c : 383 --------------------------------------------------------
06/14/19 05:21:34 - Process(62299.10) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.735Z)
                    CommentInsert1(IBM MQ Distributed Pub/Sub Publish Task)

AMQ5975I: 'IBM MQ Distributed Pub/Sub Publish Task' has started.

EXPLANATION:
'IBM MQ Distributed Pub/Sub Publish Task' has started.
ACTION:
None.
----- cmqxzmup.c : 383 --------------------------------------------------------
06/14/19 05:21:34 - Process(62321.1) User(mqm) Program(amqzmgr0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.746Z)
                    ArithInsert1(62332)
                    CommentInsert1(SYSTEM.CHANNEL.INITQ)

AMQ5022I: The channel initiator has started. ProcessId(62332).

EXPLANATION:
The channel initiator process has started.
ACTION:
None.
----- amqzmgr0.c : 2934 -------------------------------------------------------
06/14/19 05:21:34 - Process(62321.1) User(mqm) Program(amqzmgr0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.749Z)
                    ArithInsert1(62335)
                    CommentInsert1(SYSTEM.CMDSERVER.1)

AMQ5024I: The command server has started. ProcessId(62335).

EXPLANATION:
The command server process has started.
ACTION:
None.
----- amqzmgr0.c : 2943 -------------------------------------------------------
06/14/19 05:21:34 - Process(62332.1) User(mqm) Program(runmqchi)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.798Z)
                    CommentInsert1(SYSTEM.CHANNEL.INITQ)

AMQ8024I: IBM MQ channel initiator started.

EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
----- amqrimna.c : 866 --------------------------------------------------------
06/14/19 05:21:34 - Process(62324.1) User(mqm) Program(amqfqpub)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.800Z)
                    CommentInsert1(QM_TEST)

AMQ5806I: Queued Publish/Subscribe Daemon started for queue manager QM_TEST.

EXPLANATION:
Queued Publish/Subscribe Daemon started for queue manager QM_TEST.
ACTION:
None.
----- cmqxfcxc.c : 1397 -------------------------------------------------------
06/14/19 05:22:16 - Process(62321.1) User(mqm) Program(amqzmgr0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:22:16.457Z)
                    ArithInsert1(62392)
                    CommentInsert1(TCP.LISTENER)

AMQ5026I: The listener 'TCP.LISTENER' has started. ProcessId(62392).

EXPLANATION:
The listener process has started.
ACTION:
None.
----- amqzmgr0.c : 2951 -------------------------------------------------------
06/14/19 05:22:25 - Process(62392.1) User(mqm) Program(runmqlsr)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:22:25.488Z)
                    ArithInsert1(1414) ArithInsert2(98)
                    CommentInsert1(bind)
                    CommentInsert2(TCP/IP)
                    CommentInsert3(:)

AMQ9218E: The TCP/IP listener program could not bind to port number 1414.

EXPLANATION:
An attempt to bind the TCP/IP socket to the listener port was unsuccessful.
ACTION:
The failure could be due to another program, including other MQ listeners,
using the same port number. The return code from the 'bind' call for port :1414
was 98. Record these values and tell the systems administrator.
----- amqclita.c : 748 --------------------------------------------------------
06/14/19 05:22:25 - Process(62321.1) User(mqm) Program(amqzmgr0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:22:25.493Z)
                    ArithInsert1(62392)
                    CommentInsert1(TCP.LISTENER)

AMQ5027I: The listener 'TCP.LISTENER' has ended. ProcessId(62392).

EXPLANATION:
The listener process has ended.
ACTION:
None.

无法与队列管理器建立连接。无法识别通道名称 (AMQ4871) 严重性：10（警告）说明: 连接到队列管理器的尝试失败。队列管理器无法识别通道名称。

【问题讨论】：

你在 mq explorer 中指定了什么频道？
默认频道 SYSTEM.ADMIN.SVRCONN
您是否将 SYSTEM.ADMIN.SVRCONN 通道添加到您的队列管理器？
是的，我已将频道添加到队列管理器
这些命令是否也需要运行 set CHLAUTH() TYPE(BLOCKUSER) USERLIST('nobody','*MQADMIN') set CHLAUTH(SYSTEM.ADMIN.) TYPE (BLOCKUSER) USERLIST('nobody')

标签： java ibm-mq esb

【解决方案1】：

错误消息告诉您尚未在队列管理器上定义通道。如果您认为该通道已在队列管理器上定义，另一个原因可能是您的客户端（在本例中为 MQ Explorer）实际上并未连接到您认为它正在连接的队列管理器。在这种情况下，通道未定义，因为它是错误的队列管理器。

默认情况下，队列管理器上未定义 MQ Explorer 使用的默认通道，以确保它不会被未经授权的用户滥用。

如果您查看队列管理器AMQERR01.LOG，您将看到类似的错误消息，其中还列出了不存在的通道名称。

要定义通道，请使用队列管理器机器上的runmqsc 工具，然后输入以下 MQSC 命令。

DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN) DESCR('Channel for MQ Explorer connectivity')

【讨论】：

Dear check snapshots in post ，已经运行 DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN) DESCR('Channel for MQ Explorer connectivity')额外运行
如果您有另一个队列管理器在端口 1414 上侦听，那么这就是队列管理器报告它没有通道。为您的侦听器使用不同的端口。