ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexGeneral IBM MQ SupportTrouble setting up a mq client access to queue 2058

Post new topicReply to topic Goto page Previous  1, 2
Trouble setting up a mq client access to queue 2058 View previous topic :: View next topic
Author Message
fjb_saper
PostPosted: Sun Sep 24, 2017 8:45 pm Post subject: Reply with quote

Grand Poobah

Joined: 18 Nov 2003
Posts: 19296
Location: LI,NY

rib445 wrote:
I've figured out the issue. This was my second attempt at setting up a QM and my first attempt at a QM was apparently still running and listening on port 1415 (although I didn't see any errors about this), so the initial error "2058 - Q Mgr Name Error" was quite accurate. On ending this old QM and starting my new 'QM_TEST' I'm able to get and put remotely.

Thanks to everyone for helping with this.


As per the OP the port assigned to the qmgr was busy and the qmgr could not get the listener started as a listener was already running on this port for a different qmgr. Hence the 2058 wrong qmgr name....
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
rib445
PostPosted: Sun Sep 24, 2017 10:30 pm Post subject: Reply with quote

Newbie

Joined: 23 Sep 2017
Posts: 7

bruce2359 wrote:
Happy to help.

But, you have not explained exactly and precisely what the problem that is now fixed. Please share with us and others who might have the same/similar problem in the future.


I think fjb explains it well. What helped me identify the issue was when I ran "ps -ef | grep mq" which showed me all the mq process and I could see which port was associated with a QM, e.g.

Code:

mqm       8830  8814  0 Sep24 ?        00:00:00 /opt/mqm/bin/runmqlsr -r -m QM_TEST -t TCP -p 1415


This now shows the correct QM but I was seeing a different QM previously.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Mon Sep 25, 2017 4:16 pm Post subject: Reply with quote

Padawan

Joined: 25 Mar 2003
Posts: 1719
Location: Melbourne, Australia

"ps -ef | grep lsr" usually shows all the MQ listeners. It is the MQ admin's responsibility to ensure that all queue managers on a server have TCP LISTENER objects set up to use fixed and different ports, and that remote qmgrs and client channels use the assigned port. Usually they are assigned 1414, 1415, 1416 etc for the 1st, 2nd, 3rd qmgr etc.
_________________
Glenn
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Tue Sep 26, 2017 7:39 am Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1180
Location: Derby City, USA

Furthermore, always use the fully qualified DNS name. If you have any interest in being secure, implement X.509 certificate security to know that the entity connecting is who they say they are.
Back to top
View user's profile Send private message AIM Address
Display posts from previous:
Post new topicReply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum IndexGeneral IBM MQ SupportTrouble setting up a mq client access to queue 2058
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.