| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Broker on remote machine |
« View previous topic :: View next topic » |
| Author |
Message
|
| fehmees |
 Posted: Sun Mar 30, 2003 2:28 am Post subject: Broker on remote machine |
 |
|
Newbie
Joined: 10 Mar 2003
Posts: 5
|
Hi,
I am having difficulties in communicating broker on one machine to a ConfigMgr on other machine.
Here is my scenario
I have a broker running on machine A and a configMgr on machine B.
I have created the respective transmission queue with its respective Qmgr on each machine.
Both channel (SDR & REV) are running.
The problem occurs when deploy a message flow or even a new execution group on to machine A broker,
The error is seen under NT log file on Broker machine is
( MQSI_BROKER_TEST ) A problem was detected with MQSeries while issuing MQOPEN for MQSeries queue 'SYSTEM.BROKER.ADMIN.REPLY', MQSeries queue manager 'TEST.QUEUE.MANAGER'. MQCC=2, MQRC=2087.
The operation on the specified queue or queue manager returned with the indicated MQSeries completion and reason code.
&
(MQSI_BROKER_TEST ) The broker was unable to put an internal configuration message to message queue 'SYSTEM.BROKER.ADMIN.REPLY'.
The internal configuration message could not be sent because the message queue was not available.
Investigate why the message queue was not available by reviewing messages issued to the system log. Resolve the problem and redeploy the broker's configuration
I had restarted the broker, still doesn't work. An early help would be appreciated.
Thanks
[/b] |
|
| Back to top |
|
 |
| yaakovd |
| Posted: Sun Mar 30, 2003 2:57 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
Error 2087 is: UNKNOWN_REMOTE_Q_MGR
Queue 'SYSTEM.BROKER.ADMIN.REPLY' should be exist on ConfigMgr QMgr (I anderstood 'TEST.QUEUE.MANAGER') - check it.
Looks like you configuration message reached broker 'SYSTEM.BROKER.ADMIN.QUEUE' but you have problem with one of parameters on sender channel or XMitQ from Broker QMgr to ConfigMgr QMgr. Just recheck spelling.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| kirani |
| Posted: Sun Mar 30, 2003 10:29 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Please make sure that the Transmission queue name is same as other queue manager name. For example,
If your Config Mgr Qmgr name is QM1 and Broker Qmgr name is QM2, then the Transmission Queue on QM1 should be named as QM2 and Transmission Queue on QM2 should be named as QM1.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| tillywern |
| Posted: Mon Mar 31, 2003 10:31 am Post subject: Permissions |
|
|
Centurion
Joined: 28 Jan 2003
Posts: 109
Location: Colorado
|
Although the problem you described looks more like what the others described you can also run into problems if the user under shich the broker is running is not authorized to place messages on these and other queues associated with the broker.
During setup, permissions should be setup already.. But I have had similar problems when implementing brokers..
Check to ensure that your transmission queue is named the same as the configmgr queue manager name... ESPECIALLY case as the queu enames are case senesitive. |
|
| 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
|
|
|
|
