| Author |
Message
|
| Cyberherbalist |
 Posted: Thu Jul 23, 2009 3:10 pm Post subject: Multiple QM's listening on same port |
 |
|
Guest
|
Our production MQ server has two queue managers, one for production and the other for QA (staging). Oddly enough, in the MQ Explorer Properties of both QMs is the TCP port assignment 1414, though they each one's listener is listening on different ports (1414 & 1415).
I'm not sure what to think of this. Shouldn't the TCP port in the Queue Manager Properties be the same as the Listener.TCP? And what is the effect if they're the same? |
|
| Back to top |
|
 |
| manicminer |
| Posted: Thu Jul 23, 2009 11:41 pm Post subject: |
|
|
Disciple
Joined: 11 Jul 2007
Posts: 177
|
TCP port property on a queue manager is the default port, if you don't specify one for runmqlsr on the command line, or use magic port 0 in your listener object definition.
You only need to worry about it in those 2 cases. Otherwise just check the way your listener objects are defined (or how your runmqlsr commands are run)
_________________
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 24, 2009 6:08 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| manicminer wrote: |
TCP port property on a queue manager is the default port, if you don't specify one for runmqlsr on the command line, or use magic port 0 in your listener object definition.
|
That number is also what gets appended to the end of the CONNAME parm in your sending channels and CLUSRCVRs if you don't specify a port # explicitly in the channel def.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| manicminer |
| Posted: Fri Jul 24, 2009 6:26 am Post subject: |
|
|
Disciple
Joined: 11 Jul 2007
Posts: 177
|
| PeterPotkay wrote: |
That number is also what gets appended to the end of the CONNAME parm in your sending channels and CLUSRCVRs if you don't specify a port # explicitly in the channel def. |
Ah ha, you learn something new everyday 
_________________
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Jul 24, 2009 10:29 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
I highly recommend you always be specific. One day, some one will get clever and change that and go on vacation. Then, on the weekend late at night, someone will reboot that machine or recycle that QMGR. You will get a call that goes something like "MQ is broken again. Fix it! Just fix it!"
You will be wondering what is wrong. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 24, 2009 10:44 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You said a mouthful. That's why I know this. None of out channels had the (1414) at the end of the CONNAME. One day someone says, "Oh, this QM is listening on 1415, let me change that parm to match." It took a while to figure out why the channels were all going after the wrong ports.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jul 25, 2009 2:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Worse case scenario.... someone changes the default port for MQ and tells nobody... You recycle a qmgr and the channels go into retry... and not just yours, your partners as well....
This is why you should always state the channel number explicitely, on the listener, on the conname...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
