| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Two brokers on same machine. |
« View previous topic :: View next topic » |
| Author |
Message
|
| umeshs |
 Posted: Tue Apr 09, 2002 3:37 am Post subject: |
 |
|
Novice
Joined: 11 Feb 2002
Posts: 11
|
Hello All,
I am having MQSeries for Windows NT, V5.2 and MQSI Version 2.0.2 on my machine.
I have MQSI running fine for a default Queue manager on my machine(I can open and work on control center for default connection).
For some proof of concept, I have created 2 new queue managers in a cluster on same machine.
As, it was on same machine, I gave connection name as The TCP/IP loop back address 127.0.0.1 say, 127.0.0.1(1415). I am able to start the channels.
Further, I have created two brokers on same machine. I have started this new broker service from control panel -> services. Now I am not able to open the control center.
It says,
BIP1352S: MQSeries queue manager QM_2 on host system BM_22 not available.
When connecting to the MQSeries queue manager, queue manager QM_2 is not up and running and not listening for input on host system BM_22. The Control Center is unable to communicate with the Configuration Manager.
Check that the queue manager name entered in the Control Center File->Connection dialog box has been correctly specified. Start the MQSeries queue manager if it is not running. Ensure that the MQSeries listener is running and listening on the correct port, that only one listener is listening on that port. Ensure that MQSeries server connection channel SYSTEM.BKR.CONFIG is defined to the queue manager. For more information on this error, see the MQSeries Application Programming Reference manual, codes 2059, 2161, 2162, and 2009.
If I try giving host name as 127.0.0.1, It throws error
BIP1352S: MQSeries queue manager QM_2 on host system 127.0.0.1 not available.
When connecting to the MQSeries queue manager, queue manager QM_2 is not up and running and not listening for input on host system 127.0.0.1. The Control Center is unable to communicate with the Configuration Manager.
Check that the queue manager name entered in the Control Center File->Connection dialog box has been correctly specified. Start the MQSeries queue manager if it is not running. Ensure that the MQSeries listener is running and listening on the correct port, that only one listener is listening on that port. Ensure that MQSeries server connection channel SYSTEM.BKR.CONFIG is defined to the queue manager. For more information on this error, see the MQSeries Application Programming Reference manual, codes 2059, 2161, 2162, and 2009.
Please revert back if I have to do something else to run two brokers (at a time) from my machine.
Thanks in advance.
Regards,
Umesh
|
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Wed Apr 10, 2002 1:59 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Apologies if I have misunderstood the problem, but you should not have to change the values in the Connection dialog box just because you have added some brokers. The control center only connects to the configuration manager, and I assume that is on your original default queue manager (maybe on port 1414).
I have always used something like 'localhost(1414)' as my connection name. The loopback ip address should also be fine assuming the machine is set up ok - try pinging it.
Regards, Vicky |
|
| 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
|
|
|
|
