| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Creation of queue manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| exerk |
 Posted: Thu Aug 07, 2008 11:24 pm Post subject: |
 |
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Quote: |
| I am using MQ 5.3 on SuSe Linux and AIX. |
If you create a new queue manager it will not have the 'basic' port of 1414 unless you assign it that port in /etc/services and inetd, but better to script runmqlsr, far better still to upgrade to v6.0 if possible.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
 |
| SAFraser |
| Posted: Fri Aug 08, 2008 3:47 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Just because your qmgr is communicating to 'other machines', it does not mean you have a listener running. It means they each have a listener running.
Are any of them communicating to you? If the answer to that is 'yes', then what is the ouput of netstat -an |grep <that-other-machines-IP>? How about netstat -an and look for likely port numbers, like 1414, 1881, 1415, etc?
What is the output of ps -ef | grep runmqlsr?
Do not put your new queue manager's listener in etc/services, you lose the under-the-covers improvements in channel pooling in 5.3. There is no "creating" a listener. You simply execute the command. See my earlier post about parameters and such. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
