| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Multiple Queue Managers on W2k Box |
« View previous topic :: View next topic » |
| Author |
Message
|
| hkeener |
 Posted: Wed Apr 24, 2002 8:51 am Post subject: |
 |
|
Newbie
Joined: 15 Apr 2002
Posts: 5
|
I have two queue manager running on a single Win 2000 Server.
The default queue manager has a listener set to port 1414.
The second queue manager has a listener set to port 2014.
Channels are configured appropriately.
I can set my MQSERVER env variable (on any remote client machine) to point to the channel for the default queue manager and it connects fine.
I cannot however, make a remote client connection to the second queue manager
when I set the MQSERVER env variable to point to it's appropriate channel.
Anyone ever seen this problem?
Does it have something to do with the Default Queue Manager?
thks
|
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Wed Apr 24, 2002 9:04 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Did you specify the port number (2014) on the conname part of the MQSERVER variable?
Example: SET MQSERVER=MYCHANNEL/TCP/123.456.789.012(2014)
Personally I would create a client channel table file with both queue manager names spelled out (don't rely on defaults) and use that instead of the MQSERVER approach, but that's probably a very subjective thing.
Cheers,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| mrlinux |
| Posted: Wed Apr 24, 2002 9:08 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
One other possible problem are you specifing the QMGR Name, if not you need to set the Queue Manager name for the non default QMGRs.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| hkeener |
| Posted: Mon Apr 29, 2002 6:46 am Post subject: |
|
|
Newbie
Joined: 15 Apr 2002
Posts: 5
|
Thanks Guys,
Ended up that this was a firewall issue and sysadmin had closed access to all ports on the box other than a select few like 1414 .... D'oh!!!!!
The concept should work fine.
hck |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
