Connect Remote Queue Manager in a container via MQ Explorer

Question

I want to access queue manager via mq explorer but getting an error:

Could not establish a connection to the queue manager - reason 2538. (AMQ4059) Could not establish a connection to the queue manager - reason 2538. (AMQ4059)
Severity: 10 (Warning)
Explanation: The attempt to connect to the queue manager failed. This could be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken.
Response: Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.

I followed all the instructions in https://www-01.ibm.com/support/docview.wss?uid=swg21623113 in order to allow mq explorer to be able to access mq server but still no luck.

IBM MQ Server details:

Version: 8
OS: Centos
Running in a docker container
Using port 1417 since my 1414 port is not available for another MQ server
Listener is up an running and pointing port 1417
Channel is defined as it is described in the link that I shared (I disabled all security features as it is described)
I have a sample Java App that I can put/get messages and it is working fine

MQ Explorer details:

Also running in another docker container thanks to https://github.com/ibm-messaging/mq-container/tree/master/incubating/mq-explorer
I can telnet MQ Server from xterm so there is no issue about the connectivity
Although I disabled all security features, I also tried to create the same username on server as well as my xterm but it did not work either.

I was expecting to get an error message in my MQ Server to understand the issue but surprisingly there is no error message at all ...

Screenshot

Which version of MQ v8 are you using for the queue manager (for example 8.0.0.3 or 8.0.0.11)? Check that DIS QMGR CHLEV is set to ENABLED if it is not, then enable it with ALTER QMGR CHLEV(ENABLED). Reproduce the failure and check to see any messages are generated in the SYSTEM.ADMIN.CHANNEL.EVENT queue. If you see messages then run this: /opt/mqm/samp/bin/amqsevt -m QMGRNAME -q SYSTEM.ADMIN.CHANNEL.EVENT. Look at the last few messages to see if they correspond to your MQ Explorer and explain why you see a failure. — JoshMc
Both the comment from @JoshMc and the answer from Roger are suggesting you are having security issues, but reason code 2358 is MQRC_HOST_NOT_AVAILABLE, so you should double check your connectivity. You have suggested that you have not got connectivity issues because you can telnet to the QMgr - is this telnet from the same machine/docker container as the MQ Explorer is running in? You don't show us a screen shot of your MQ Explorer connection settings - we can only assume you have input the correct port there? — Morag Hughson
@JoshMc, many thanks for the advice! I followed your recommendations and as you mentioned, a record appeared in SYSTEM.ADMIN.CHANNEL.EVENT queue. Unfortunately, I do not have amqsevt script. I do have /opt/mqm/samp folder but no bin folder. I also check /opt/mqm/bin folder too but no luck. I will try to find amqsevt. Many thanks for the tip! — penny
@JoshMc, I should tell you my steps since I have feeling that the message in the queue might not be related to my issue. I changed CHLEV value in my queue manager and tried to login from mq explorer again. Nothing happened. Then, I thought that I should restart my queue manager so I did. Then, started my listener and then I thought I should start my channel as well since it is necesary for remote queue so I thought that it might be a requirement for mq explorer as well .. Anyway, I think the message in SYSTEM.ADMIN.CHANNEL.EVENT is most likely from my start channel command :( — penny
@JoshMc, I just stopped/started my channel and the number of messages becomes 3 — penny

Rob Parker Rob Parker · Accepted Answer · 2019-03-11T10:36:36

You've stated that your queue manager(s) are running in a container and your MQ Explorer is running in another container. I've noticed you've supplied 0.0.0.0 as your hostname but the container where MQ Explorer is running has no queue managers running on it!

If you run the following command (replacing with the ID of the container running your queue managers) you should get the IP address of the container on the docker subnet. Try using that IP address in MQ Explorer instead of 0.0.0.0:

docker inspect --format "{{ .NetworkSettings.IPAddress }}" <QM container>

If your container is on a different docker network then you will need to run the following replacing with the name you gave the docker network:

docker inspect --format "{{ .NetworkSettings.Networks.<Network Name>.IPAddress }}" <QM container>

Additionally, when you created your queue manager container did you remember to expose the 1417 port you are trying to use? By default the mq-container sample only exposes the following ports: 1414, 9157 & 9443. When you ran the container you would of needed to expose the ports but supplying --publish-all --publish 1417 when you ran the container. For example:

docker run -d -e LICENSE=accept --publish-all --publish 1417 ibmcom/mq

Connect Remote Queue Manager in a container via MQ Explorer

3 Answers