Connect Remote Queue Manager in a container via MQ Explorer Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Data science time! April 2019 and salary with experience The Ask Question Wizard is Live!Can create Websphere Queue Manager but not connect“Base queue manager name” in Websphere MQ Explorer/create remote queue manager in Websphere MQHow to connect from client to IBM WebSphere Queue Manager using SSL ConnectionWebSphere MQ Explorer Cannot Connect | Error AMQ4043Remote Queue Manager backup using dmpmqcfg is not workingHow to Connect to a Remote Queue Manager with IBM WebSphere MQ Explorer?How to connect to remote Queue Manager using MQExplorer 8.0websphere queue connection factory - Test connection - not working set up issuesConnection is not established between Eclipse Paho and IBM Websphere MQ
If Windows 7 doesn't support WSL, then what is "Subsystem for UNIX-based Applications"?
What does it mean that physics no longer uses mechanical models to describe phenomena?
Is it possible for SQL statements to execute concurrently within a single session in SQL Server?
What is an "asse" in Elizabethan English?
How can I prevent/balance waiting and turtling as a response to cooldown mechanics
Converted a Scalar function to a TVF function for parallel execution-Still running in Serial mode
The Nth Gryphon Number
Why are vacuum tubes still used in amateur radios?
Should a wizard buy fine inks every time he want to copy spells into his spellbook?
Getting prompted for verification code but where do I put it in?
What to do with repeated rejections for phd position
Why do early math courses focus on the cross sections of a cone and not on other 3D objects?
As Singapore Airlines (Krisflyer) Gold, can I bring my family into the lounge on a domestic Virgin Australia flight?
How does light 'choose' between wave and particle behaviour?
Significance of Cersei's obsession with elephants?
Sum letters are not two different
What's the point of the test set?
An adverb for when you're not exaggerating
Google .dev domain strangely redirects to https
What are the discoveries that have been possible with the rejection of positivism?
How could we fake a moon landing now?
Is there hard evidence that the grant peer review system performs significantly better than random?
Deconstruction is ambiguous
What is the difference between a "ranged attack" and a "ranged weapon attack"?
Connect Remote Queue Manager in a container via MQ Explorer
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Data science time! April 2019 and salary with experience
The Ask Question Wizard is Live!Can create Websphere Queue Manager but not connect“Base queue manager name” in Websphere MQ Explorer/create remote queue manager in Websphere MQHow to connect from client to IBM WebSphere Queue Manager using SSL ConnectionWebSphere MQ Explorer Cannot Connect | Error AMQ4043Remote Queue Manager backup using dmpmqcfg is not workingHow to Connect to a Remote Queue Manager with IBM WebSphere MQ Explorer?How to connect to remote Queue Manager using MQExplorer 8.0websphere queue connection factory - Test connection - not working set up issuesConnection is not established between Eclipse Paho and IBM Websphere MQ
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
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
ibm-mq
edited Mar 11 at 16:13
Rob Parker
513414
asked Mar 8 at 21:40
pennypenny
134
|
show 6 more comments
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
ibm-mq
edited Mar 11 at 16:13
Rob Parker
513414
asked Mar 8 at 21:40
pennypenny
134
Which version of MQ v8 are you using for the queue manager (for example 8.0.0.3 or 8.0.0.11)? Check thatDIS QMGR CHLEVis set toENABLEDif it is not, then enable it withALTER QMGR CHLEV(ENABLED). Reproduce the failure and check to see any messages are generated in theSYSTEM.ADMIN.CHANNEL.EVENTqueue. 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
Mar 9 at 0:45
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
Mar 9 at 4:05
@JoshMc, many thanks for the advice! I followed your recommendations and as you mentioned, a record appeared inSYSTEM.ADMIN.CHANNEL.EVENTqueue. Unfortunately, I do not haveamqsevtscript. I do have/opt/mqm/sampfolder but nobinfolder. I also check/opt/mqm/binfolder too but no luck. I will try to findamqsevt. Many thanks for the tip!
– penny
Mar 10 at 6:59
@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 changedCHLEVvalue 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 inSYSTEM.ADMIN.CHANNEL.EVENTis most likely from my start channel command :(
– penny
Mar 10 at 7:20
@JoshMc, I just stopped/started my channel and the number of messages becomes 3
– penny
Mar 10 at 7:23
|
show 6 more comments
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
ibm-mq
edited Mar 11 at 16:13
Rob Parker
513414
asked Mar 8 at 21:40
pennypenny
134
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
ibm-mq
ibm-mq
edited Mar 11 at 16:13
Rob Parker
513414
asked Mar 8 at 21:40
pennypenny
134
edited Mar 11 at 16:13
Rob Parker
513414
asked Mar 8 at 21:40
pennypenny
134
edited Mar 11 at 16:13
Rob Parker
513414
edited Mar 11 at 16:13
Rob Parker
513414
edited Mar 11 at 16:13
Rob Parker
513414
513414
asked Mar 8 at 21:40
pennypenny
134
asked Mar 8 at 21:40
pennypenny
134
asked Mar 8 at 21:40
pennypenny
134
134
Which version of MQ v8 are you using for the queue manager (for example 8.0.0.3 or 8.0.0.11)? Check thatDIS QMGR CHLEVis set toENABLEDif it is not, then enable it withALTER QMGR CHLEV(ENABLED). Reproduce the failure and check to see any messages are generated in theSYSTEM.ADMIN.CHANNEL.EVENTqueue. 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
Mar 9 at 0:45
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
Mar 9 at 4:05
@JoshMc, many thanks for the advice! I followed your recommendations and as you mentioned, a record appeared inSYSTEM.ADMIN.CHANNEL.EVENTqueue. Unfortunately, I do not haveamqsevtscript. I do have/opt/mqm/sampfolder but nobinfolder. I also check/opt/mqm/binfolder too but no luck. I will try to findamqsevt. Many thanks for the tip!
– penny
Mar 10 at 6:59
@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 changedCHLEVvalue 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 inSYSTEM.ADMIN.CHANNEL.EVENTis most likely from my start channel command :(
– penny
Mar 10 at 7:20
@JoshMc, I just stopped/started my channel and the number of messages becomes 3
– penny
Mar 10 at 7:23
|
show 6 more comments
Which version of MQ v8 are you using for the queue manager (for example 8.0.0.3 or 8.0.0.11)? Check thatDIS QMGR CHLEVis set toENABLEDif it is not, then enable it withALTER QMGR CHLEV(ENABLED). Reproduce the failure and check to see any messages are generated in theSYSTEM.ADMIN.CHANNEL.EVENTqueue. 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
Mar 9 at 0:45
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
Mar 9 at 4:05
@JoshMc, many thanks for the advice! I followed your recommendations and as you mentioned, a record appeared inSYSTEM.ADMIN.CHANNEL.EVENTqueue. Unfortunately, I do not haveamqsevtscript. I do have/opt/mqm/sampfolder but nobinfolder. I also check/opt/mqm/binfolder too but no luck. I will try to findamqsevt. Many thanks for the tip!
– penny
Mar 10 at 6:59
@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 changedCHLEVvalue 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 inSYSTEM.ADMIN.CHANNEL.EVENTis most likely from my start channel command :(
– penny
Mar 10 at 7:20
@JoshMc, I just stopped/started my channel and the number of messages becomes 3
– penny
Mar 10 at 7:23
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
Mar 9 at 0:45
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
Mar 9 at 0:45
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
Mar 9 at 4:05
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
Mar 9 at 4:05
@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
Mar 10 at 6:59
@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
Mar 10 at 6:59
@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
Mar 10 at 7:20
@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
Mar 10 at 7:20
@JoshMc, I just stopped/started my channel and the number of messages becomes 3
– penny
Mar 10 at 7:23
@JoshMc, I just stopped/started my channel and the number of messages becomes 3
– penny
Mar 10 at 7:23
|
show 6 more comments
3 Answers
3
active
oldest
votes
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
answered Mar 11 at 10:36
Rob ParkerRob Parker
513414
Many thanks Rob! This solved my problem. Just to be clear, I have already published port 1417 to my host but I was using 0.0.0.0 instead of 172.17.0.2
– penny
Mar 12 at 16:48
How can I mark this as solved?
– penny
Mar 12 at 16:58
Glad to hear it solved your problem. This slack overflow document details what to do when someone answers a question and how to mark the problem as solved: stackoverflow.com/help/someone-answers In this case you should "accept" this answer to show it fixed your problem.
– Rob Parker
Mar 12 at 20:49
add a comment |
You don't say what version of IBM MQ your queue manager is running under. i.e. v7.5, v8.0, v9.0 or v9.1.
Did you give yourself CHLAUTH permission to use the SYSTEM.ADMIN.SVRCONN channel? Most likely you are being blocked by the backstop rule.
Also, if you are on IBM MQ v8.0 or higher then then CONNAUTH could be blocking you.
Here are 2 good links to walk you through your issue.
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/blocked_by_chlauth_why?lang=en
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q001110_.htm
answered Mar 8 at 23:14
RogerRoger
4,869714
MQ version is 8.0.0.4. In the link that I shared (www-01.ibm.com/support/docview.wss?uid=swg21623113), it recommends: * c. For MQ 7.1 and later, and if you need to allow remote connections by an MQ Administrator. * d. For MQ 8.0 and later, and if you want the password to be optional for an MQ Administrator. * I did both of them so CONNAUTH is not an issue for me but I will take a look to your link in case I might catch something. Thanks a lot for the reply
– penny
Mar 10 at 7:06
I just read the links but they are all related if CHLAUTH(ENABLED) which is not the case for me.
– penny
Mar 10 at 7:32
add a comment |
You have attempted to connect your MQ Explorer to your queue manager using the following connection details:-
- Host name or IP address: 0.0.0.0
- Port number: 1417
- Server-connection channel: SYSTEM.ADMIN.SVRCONN
and you have received return code MQRC_HOST_NOT_AVAILABLE(2358) which says that the network address is not reachable.
Common reasons for this error include not having a TCP.IP listener running using that port, but you have told us you have got a listener running.
The IP address you have used is the problem. Change the IP address in your MQ Explorer configuration to the actual IP address where the queue manager is running. If the MQ Explorer and Queue Manager are on the same machine (in the same container), you can use the localhost hostname or the IP address 127.0.0.1, otherwise, please use the assigned IP address for the machine. From your screenshot it appears that this might be a 192.168.* address.
answered Mar 10 at 21:22
Morag HughsonMorag Hughson
4,685832
0.0.0.0 seems to be a docker reference to the real ip of the host from what i read. Unless you tell docker to route a host port to the docker ip it does not.
– JoshMc
Mar 10 at 22:02
On a normal linux host 0.0.0.0 went to 127.0.0.1 for me.
– JoshMc
Mar 10 at 22:08
On Windows it doesn't seem to be setup by default.
– Morag Hughson
Mar 11 at 2:43
Not sure from your comments whether you think this is or is not the problem?
– Morag Hughson
Mar 11 at 2:43
I think it may have to do with the container ports that are exposed or not exposed.
– JoshMc
Mar 11 at 3:59
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55071393%2fconnect-remote-queue-manager-in-a-container-via-mq-explorer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
answered Mar 11 at 10:36
Rob ParkerRob Parker
513414
Many thanks Rob! This solved my problem. Just to be clear, I have already published port 1417 to my host but I was using 0.0.0.0 instead of 172.17.0.2
– penny
Mar 12 at 16:48
How can I mark this as solved?
– penny
Mar 12 at 16:58
Glad to hear it solved your problem. This slack overflow document details what to do when someone answers a question and how to mark the problem as solved: stackoverflow.com/help/someone-answers In this case you should "accept" this answer to show it fixed your problem.
– Rob Parker
Mar 12 at 20:49
add a comment |
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
answered Mar 11 at 10:36
Rob ParkerRob Parker
513414
Many thanks Rob! This solved my problem. Just to be clear, I have already published port 1417 to my host but I was using 0.0.0.0 instead of 172.17.0.2
– penny
Mar 12 at 16:48
How can I mark this as solved?
– penny
Mar 12 at 16:58
Glad to hear it solved your problem. This slack overflow document details what to do when someone answers a question and how to mark the problem as solved: stackoverflow.com/help/someone-answers In this case you should "accept" this answer to show it fixed your problem.
– Rob Parker
Mar 12 at 20:49
add a comment |
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
answered Mar 11 at 10:36
Rob ParkerRob Parker
513414
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
answered Mar 11 at 10:36
Rob ParkerRob Parker
513414
answered Mar 11 at 10:36
Rob ParkerRob Parker
513414
answered Mar 11 at 10:36
Rob ParkerRob Parker
513414
answered Mar 11 at 10:36
Rob ParkerRob Parker
513414
513414
Many thanks Rob! This solved my problem. Just to be clear, I have already published port 1417 to my host but I was using 0.0.0.0 instead of 172.17.0.2
– penny
Mar 12 at 16:48
How can I mark this as solved?
– penny
Mar 12 at 16:58
Glad to hear it solved your problem. This slack overflow document details what to do when someone answers a question and how to mark the problem as solved: stackoverflow.com/help/someone-answers In this case you should "accept" this answer to show it fixed your problem.
– Rob Parker
Mar 12 at 20:49
add a comment |
Many thanks Rob! This solved my problem. Just to be clear, I have already published port 1417 to my host but I was using 0.0.0.0 instead of 172.17.0.2
– penny
Mar 12 at 16:48
How can I mark this as solved?
– penny
Mar 12 at 16:58
Glad to hear it solved your problem. This slack overflow document details what to do when someone answers a question and how to mark the problem as solved: stackoverflow.com/help/someone-answers In this case you should "accept" this answer to show it fixed your problem.
– Rob Parker
Mar 12 at 20:49
Many thanks Rob! This solved my problem. Just to be clear, I have already published port 1417 to my host but I was using 0.0.0.0 instead of 172.17.0.2
– penny
Mar 12 at 16:48
Many thanks Rob! This solved my problem. Just to be clear, I have already published port 1417 to my host but I was using 0.0.0.0 instead of 172.17.0.2
– penny
Mar 12 at 16:48
How can I mark this as solved?
– penny
Mar 12 at 16:58
How can I mark this as solved?
– penny
Mar 12 at 16:58
Glad to hear it solved your problem. This slack overflow document details what to do when someone answers a question and how to mark the problem as solved: stackoverflow.com/help/someone-answers In this case you should "accept" this answer to show it fixed your problem.
– Rob Parker
Mar 12 at 20:49
Glad to hear it solved your problem. This slack overflow document details what to do when someone answers a question and how to mark the problem as solved: stackoverflow.com/help/someone-answers In this case you should "accept" this answer to show it fixed your problem.
– Rob Parker
Mar 12 at 20:49
add a comment |
You don't say what version of IBM MQ your queue manager is running under. i.e. v7.5, v8.0, v9.0 or v9.1.
Did you give yourself CHLAUTH permission to use the SYSTEM.ADMIN.SVRCONN channel? Most likely you are being blocked by the backstop rule.
Also, if you are on IBM MQ v8.0 or higher then then CONNAUTH could be blocking you.
Here are 2 good links to walk you through your issue.
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/blocked_by_chlauth_why?lang=en
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q001110_.htm
answered Mar 8 at 23:14
RogerRoger
4,869714
MQ version is 8.0.0.4. In the link that I shared (www-01.ibm.com/support/docview.wss?uid=swg21623113), it recommends: * c. For MQ 7.1 and later, and if you need to allow remote connections by an MQ Administrator. * d. For MQ 8.0 and later, and if you want the password to be optional for an MQ Administrator. * I did both of them so CONNAUTH is not an issue for me but I will take a look to your link in case I might catch something. Thanks a lot for the reply
– penny
Mar 10 at 7:06
I just read the links but they are all related if CHLAUTH(ENABLED) which is not the case for me.
– penny
Mar 10 at 7:32
add a comment |
You don't say what version of IBM MQ your queue manager is running under. i.e. v7.5, v8.0, v9.0 or v9.1.
Did you give yourself CHLAUTH permission to use the SYSTEM.ADMIN.SVRCONN channel? Most likely you are being blocked by the backstop rule.
Also, if you are on IBM MQ v8.0 or higher then then CONNAUTH could be blocking you.
Here are 2 good links to walk you through your issue.
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/blocked_by_chlauth_why?lang=en
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q001110_.htm
answered Mar 8 at 23:14
RogerRoger
4,869714
MQ version is 8.0.0.4. In the link that I shared (www-01.ibm.com/support/docview.wss?uid=swg21623113), it recommends: * c. For MQ 7.1 and later, and if you need to allow remote connections by an MQ Administrator. * d. For MQ 8.0 and later, and if you want the password to be optional for an MQ Administrator. * I did both of them so CONNAUTH is not an issue for me but I will take a look to your link in case I might catch something. Thanks a lot for the reply
– penny
Mar 10 at 7:06
I just read the links but they are all related if CHLAUTH(ENABLED) which is not the case for me.
– penny
Mar 10 at 7:32
add a comment |
You don't say what version of IBM MQ your queue manager is running under. i.e. v7.5, v8.0, v9.0 or v9.1.
Did you give yourself CHLAUTH permission to use the SYSTEM.ADMIN.SVRCONN channel? Most likely you are being blocked by the backstop rule.
Also, if you are on IBM MQ v8.0 or higher then then CONNAUTH could be blocking you.
Here are 2 good links to walk you through your issue.
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/blocked_by_chlauth_why?lang=en
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q001110_.htm
answered Mar 8 at 23:14
RogerRoger
4,869714
You don't say what version of IBM MQ your queue manager is running under. i.e. v7.5, v8.0, v9.0 or v9.1.
Did you give yourself CHLAUTH permission to use the SYSTEM.ADMIN.SVRCONN channel? Most likely you are being blocked by the backstop rule.
Also, if you are on IBM MQ v8.0 or higher then then CONNAUTH could be blocking you.
Here are 2 good links to walk you through your issue.
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/blocked_by_chlauth_why?lang=en
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q001110_.htm
answered Mar 8 at 23:14
RogerRoger
4,869714
answered Mar 8 at 23:14
RogerRoger
4,869714
answered Mar 8 at 23:14
RogerRoger
4,869714
answered Mar 8 at 23:14
RogerRoger
4,869714
4,869714
MQ version is 8.0.0.4. In the link that I shared (www-01.ibm.com/support/docview.wss?uid=swg21623113), it recommends: * c. For MQ 7.1 and later, and if you need to allow remote connections by an MQ Administrator. * d. For MQ 8.0 and later, and if you want the password to be optional for an MQ Administrator. * I did both of them so CONNAUTH is not an issue for me but I will take a look to your link in case I might catch something. Thanks a lot for the reply
– penny
Mar 10 at 7:06
I just read the links but they are all related if CHLAUTH(ENABLED) which is not the case for me.
– penny
Mar 10 at 7:32
add a comment |
MQ version is 8.0.0.4. In the link that I shared (www-01.ibm.com/support/docview.wss?uid=swg21623113), it recommends: * c. For MQ 7.1 and later, and if you need to allow remote connections by an MQ Administrator. * d. For MQ 8.0 and later, and if you want the password to be optional for an MQ Administrator. * I did both of them so CONNAUTH is not an issue for me but I will take a look to your link in case I might catch something. Thanks a lot for the reply
– penny
Mar 10 at 7:06
I just read the links but they are all related if CHLAUTH(ENABLED) which is not the case for me.
– penny
Mar 10 at 7:32
MQ version is 8.0.0.4. In the link that I shared (www-01.ibm.com/support/docview.wss?uid=swg21623113), it recommends: * c. For MQ 7.1 and later, and if you need to allow remote connections by an MQ Administrator. * d. For MQ 8.0 and later, and if you want the password to be optional for an MQ Administrator. * I did both of them so CONNAUTH is not an issue for me but I will take a look to your link in case I might catch something. Thanks a lot for the reply
– penny
Mar 10 at 7:06
MQ version is 8.0.0.4. In the link that I shared (www-01.ibm.com/support/docview.wss?uid=swg21623113), it recommends: * c. For MQ 7.1 and later, and if you need to allow remote connections by an MQ Administrator. * d. For MQ 8.0 and later, and if you want the password to be optional for an MQ Administrator. * I did both of them so CONNAUTH is not an issue for me but I will take a look to your link in case I might catch something. Thanks a lot for the reply
– penny
Mar 10 at 7:06
I just read the links but they are all related if CHLAUTH(ENABLED) which is not the case for me.
– penny
Mar 10 at 7:32
I just read the links but they are all related if CHLAUTH(ENABLED) which is not the case for me.
– penny
Mar 10 at 7:32
add a comment |
You have attempted to connect your MQ Explorer to your queue manager using the following connection details:-
- Host name or IP address: 0.0.0.0
- Port number: 1417
- Server-connection channel: SYSTEM.ADMIN.SVRCONN
and you have received return code MQRC_HOST_NOT_AVAILABLE(2358) which says that the network address is not reachable.
Common reasons for this error include not having a TCP.IP listener running using that port, but you have told us you have got a listener running.
The IP address you have used is the problem. Change the IP address in your MQ Explorer configuration to the actual IP address where the queue manager is running. If the MQ Explorer and Queue Manager are on the same machine (in the same container), you can use the localhost hostname or the IP address 127.0.0.1, otherwise, please use the assigned IP address for the machine. From your screenshot it appears that this might be a 192.168.* address.
answered Mar 10 at 21:22
Morag HughsonMorag Hughson
4,685832
0.0.0.0 seems to be a docker reference to the real ip of the host from what i read. Unless you tell docker to route a host port to the docker ip it does not.
– JoshMc
Mar 10 at 22:02
On a normal linux host 0.0.0.0 went to 127.0.0.1 for me.
– JoshMc
Mar 10 at 22:08
On Windows it doesn't seem to be setup by default.
– Morag Hughson
Mar 11 at 2:43
Not sure from your comments whether you think this is or is not the problem?
– Morag Hughson
Mar 11 at 2:43
I think it may have to do with the container ports that are exposed or not exposed.
– JoshMc
Mar 11 at 3:59
add a comment |
You have attempted to connect your MQ Explorer to your queue manager using the following connection details:-
- Host name or IP address: 0.0.0.0
- Port number: 1417
- Server-connection channel: SYSTEM.ADMIN.SVRCONN
and you have received return code MQRC_HOST_NOT_AVAILABLE(2358) which says that the network address is not reachable.
Common reasons for this error include not having a TCP.IP listener running using that port, but you have told us you have got a listener running.
The IP address you have used is the problem. Change the IP address in your MQ Explorer configuration to the actual IP address where the queue manager is running. If the MQ Explorer and Queue Manager are on the same machine (in the same container), you can use the localhost hostname or the IP address 127.0.0.1, otherwise, please use the assigned IP address for the machine. From your screenshot it appears that this might be a 192.168.* address.
answered Mar 10 at 21:22
Morag HughsonMorag Hughson
4,685832
0.0.0.0 seems to be a docker reference to the real ip of the host from what i read. Unless you tell docker to route a host port to the docker ip it does not.
– JoshMc
Mar 10 at 22:02
On a normal linux host 0.0.0.0 went to 127.0.0.1 for me.
– JoshMc
Mar 10 at 22:08
On Windows it doesn't seem to be setup by default.
– Morag Hughson
Mar 11 at 2:43
Not sure from your comments whether you think this is or is not the problem?
– Morag Hughson
Mar 11 at 2:43
I think it may have to do with the container ports that are exposed or not exposed.
– JoshMc
Mar 11 at 3:59
add a comment |
You have attempted to connect your MQ Explorer to your queue manager using the following connection details:-
- Host name or IP address: 0.0.0.0
- Port number: 1417
- Server-connection channel: SYSTEM.ADMIN.SVRCONN
and you have received return code MQRC_HOST_NOT_AVAILABLE(2358) which says that the network address is not reachable.
Common reasons for this error include not having a TCP.IP listener running using that port, but you have told us you have got a listener running.
The IP address you have used is the problem. Change the IP address in your MQ Explorer configuration to the actual IP address where the queue manager is running. If the MQ Explorer and Queue Manager are on the same machine (in the same container), you can use the localhost hostname or the IP address 127.0.0.1, otherwise, please use the assigned IP address for the machine. From your screenshot it appears that this might be a 192.168.* address.
answered Mar 10 at 21:22
Morag HughsonMorag Hughson
4,685832
You have attempted to connect your MQ Explorer to your queue manager using the following connection details:-
- Host name or IP address: 0.0.0.0
- Port number: 1417
- Server-connection channel: SYSTEM.ADMIN.SVRCONN
and you have received return code MQRC_HOST_NOT_AVAILABLE(2358) which says that the network address is not reachable.
Common reasons for this error include not having a TCP.IP listener running using that port, but you have told us you have got a listener running.
The IP address you have used is the problem. Change the IP address in your MQ Explorer configuration to the actual IP address where the queue manager is running. If the MQ Explorer and Queue Manager are on the same machine (in the same container), you can use the localhost hostname or the IP address 127.0.0.1, otherwise, please use the assigned IP address for the machine. From your screenshot it appears that this might be a 192.168.* address.
answered Mar 10 at 21:22
Morag HughsonMorag Hughson
4,685832
answered Mar 10 at 21:22
Morag HughsonMorag Hughson
4,685832
answered Mar 10 at 21:22
Morag HughsonMorag Hughson
4,685832
answered Mar 10 at 21:22
Morag HughsonMorag Hughson
4,685832
4,685832
0.0.0.0 seems to be a docker reference to the real ip of the host from what i read. Unless you tell docker to route a host port to the docker ip it does not.
– JoshMc
Mar 10 at 22:02
On a normal linux host 0.0.0.0 went to 127.0.0.1 for me.
– JoshMc
Mar 10 at 22:08
On Windows it doesn't seem to be setup by default.
– Morag Hughson
Mar 11 at 2:43
Not sure from your comments whether you think this is or is not the problem?
– Morag Hughson
Mar 11 at 2:43
I think it may have to do with the container ports that are exposed or not exposed.
– JoshMc
Mar 11 at 3:59
add a comment |
0.0.0.0 seems to be a docker reference to the real ip of the host from what i read. Unless you tell docker to route a host port to the docker ip it does not.
– JoshMc
Mar 10 at 22:02
On a normal linux host 0.0.0.0 went to 127.0.0.1 for me.
– JoshMc
Mar 10 at 22:08
On Windows it doesn't seem to be setup by default.
– Morag Hughson
Mar 11 at 2:43
Not sure from your comments whether you think this is or is not the problem?
– Morag Hughson
Mar 11 at 2:43
I think it may have to do with the container ports that are exposed or not exposed.
– JoshMc
Mar 11 at 3:59
0.0.0.0 seems to be a docker reference to the real ip of the host from what i read. Unless you tell docker to route a host port to the docker ip it does not.
– JoshMc
Mar 10 at 22:02
0.0.0.0 seems to be a docker reference to the real ip of the host from what i read. Unless you tell docker to route a host port to the docker ip it does not.
– JoshMc
Mar 10 at 22:02
On a normal linux host 0.0.0.0 went to 127.0.0.1 for me.
– JoshMc
Mar 10 at 22:08
On a normal linux host 0.0.0.0 went to 127.0.0.1 for me.
– JoshMc
Mar 10 at 22:08
On Windows it doesn't seem to be setup by default.
– Morag Hughson
Mar 11 at 2:43
On Windows it doesn't seem to be setup by default.
– Morag Hughson
Mar 11 at 2:43
Not sure from your comments whether you think this is or is not the problem?
– Morag Hughson
Mar 11 at 2:43
Not sure from your comments whether you think this is or is not the problem?
– Morag Hughson
Mar 11 at 2:43
I think it may have to do with the container ports that are exposed or not exposed.
– JoshMc
Mar 11 at 3:59
I think it may have to do with the container ports that are exposed or not exposed.
– JoshMc
Mar 11 at 3:59
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55071393%2fconnect-remote-queue-manager-in-a-container-via-mq-explorer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
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 CHLEVis set toENABLEDif it is not, then enable it withALTER QMGR CHLEV(ENABLED). Reproduce the failure and check to see any messages are generated in theSYSTEM.ADMIN.CHANNEL.EVENTqueue. 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
Mar 9 at 0:45
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
Mar 9 at 4:05
@JoshMc, many thanks for the advice! I followed your recommendations and as you mentioned, a record appeared in
SYSTEM.ADMIN.CHANNEL.EVENTqueue. Unfortunately, I do not haveamqsevtscript. I do have/opt/mqm/sampfolder but nobinfolder. I also check/opt/mqm/binfolder too but no luck. I will try to findamqsevt. Many thanks for the tip!– penny
Mar 10 at 6:59
@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
CHLEVvalue 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 inSYSTEM.ADMIN.CHANNEL.EVENTis most likely from my start channel command :(– penny
Mar 10 at 7:20
@JoshMc, I just stopped/started my channel and the number of messages becomes 3
– penny
Mar 10 at 7:23