| Author |
Message
|
| rmah |
 Posted: Fri Aug 10, 2007 5:12 pm Post subject: Deploying bar in clustered environment - SOLVED |
 |
|
Centurion
Joined: 04 May 2007
Posts: 142
|
Emergency....
We're having trouble delpoying bar file(s) in a clustered environment. The config mgr and broker are on 2 seperate queue managers. There are sender and receiver channels setup between the two and transmission queues are in place. The sender and receiver channels are running.
However, we're having trouble deploying bar files into exec groups. The error message is
A problem was detected with WebSphere MQ while issuing MQOPEN for WebSphere MQ queue 'SYSTEM.BROKER.ADMIN.REPLY', WebSphere MQ queue manager 'mqconfig_01'. MQCC=2, MQRC=2087
Any thoughts would be greatly appreciated....thanks!
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux
Last edited by rmah on Wed Aug 22, 2007 3:32 pm; edited 1 time in total |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Aug 10, 2007 7:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Read the intercommunications channel...
You need a DEFAULT routing from the broker to the configmgr.
So if your xmitq is not the name of the configmgr's qmgr you need to create a qmgr alias... 
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rmah |
| Posted: Fri Aug 10, 2007 7:22 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| fjb_saper wrote: |
Read the intercommunications channel...
You need a DEFAULT routing from the broker to the configmgr.
So if your xmitq is not the name of the configmgr's qmgr you need to create a qmgr alias...
Enjoy |
The xmitq on the configmgr qm and broker qm is named the same: mqbroker_01. The sender channel on teh configmgr qm and the sender channel on the broker qm uses this xmitq.
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Aug 10, 2007 7:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rmah wrote: |
| fjb_saper wrote: |
Read the intercommunications channel...
You need a DEFAULT routing from the broker to the configmgr.
So if your xmitq is not the name of the configmgr's qmgr you need to create a qmgr alias...
Enjoy |
The xmitq on the configmgr qm and broker qm is named the same: mqbroker_01. The sender channel on teh configmgr qm and the sender channel on the broker qm uses this xmitq. |
If the xmitq is named mqbroker_01 on both broker and configmgr you do not have a standard setup. Read up on the intercommunications manual...
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rmah |
| Posted: Wed Aug 22, 2007 3:31 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| fjb_saper wrote: |
| rmah wrote: |
| fjb_saper wrote: |
Read the intercommunications channel...
You need a DEFAULT routing from the broker to the configmgr.
So if your xmitq is not the name of the configmgr's qmgr you need to create a qmgr alias...
Enjoy |
The xmitq on the configmgr qm and broker qm is named the same: mqbroker_01. The sender channel on teh configmgr qm and the sender channel on the broker qm uses this xmitq. |
If the xmitq is named mqbroker_01 on both broker and configmgr you do not have a standard setup. Read up on the intercommunications manual...
Enjoy |
Solved. The transmission queue on each end has to be the same name as the destination queue manager name.
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
|
|
