| Author |
Message
|
| pfaulkner |
 Posted: Mon Mar 24, 2003 5:16 pm Post subject: SYSTEM.BROKER.* queues |
 |
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
| I had to delete my qmgr and rebuild it. After restart my BROKER (on AIX) I noticed that I didn't have any of my SYSTEM.BROKER.* queues any more. Is there something I can run to recreate them and assign the correct security to them? |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Mon Mar 24, 2003 8:05 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
They reappear on your qm when you successfully create and deploy a broker with message flows on this qm.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| pfaulkner |
| Posted: Tue Mar 25, 2003 7:11 am Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
| I already had a BROKER before I deleted the qmgr, does this mean I need to create it again? |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Mar 25, 2003 7:26 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Ok here it goes...
You start your qm.
Create your broker.
Deploy the broker and the message flows.
system.broker.* queues get created.
Now you end your qm and your broker.
Delete the qm, and hence deleting the system.broker.* queues.
Broker is not deleted.
You recreate your qm.
This does not mean that your system.broker.* queues would be available. They would only be available when you deploy your broker again on this qm with some message flows to process something. This is the time when your system.broker.* queues would reappear.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| pfaulkner |
| Posted: Tue Mar 25, 2003 8:17 am Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
I get 2085 errors on the mqsistart BROKER for:
SYSTEM.BROKER.EXECUTIONGROUP.QUEUE
SYSTEM.BROKER.CONTROL.QUEUE
and 2085 errors when I try to deploy my existing MsgFlows for:
SYSTEM.BROKER.ADMIN.QUEUE |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Mar 25, 2003 9:08 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Well, in this case what happened was.
you created your qm.
created your broker which created all the broker queues.
deployed the borker and the message flow.
Deleted the qm
recreated the qm.
but the queues are deleted.
now you try to deploy your broker on this new qm which does not have the queues any more, which is not possible(per my understanding and knowledge).
The only way you can get around this is to recreate your broker and message flows. Because each broker is attached to a queue manager. And when you delete the qm itself, broker has no significance and you cannot use it again after recreating the qm.
My $0.02 Cents.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| pfaulkner |
| Posted: Tue Mar 25, 2003 9:42 am Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
| I rebuilt all the queues manually and it looks like I'm back in business. Not sure what other problems I will run into doing it this way but for now it seems ok. |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Mar 25, 2003 8:16 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Paul,
It's a good idea to backup all your queue definitions (including SYSTEM.BROKER.*) after you setup your broker. I don't think these queue's have any "special settings" so if you create them by hand, it should work just fine.
Just make sure you increase the maximum message length on these queue's to greater than 4K ... just in case.
_________________
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 |
|
|
| pfaulkner |
| Posted: Tue Mar 25, 2003 8:50 pm Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
Yeah, I'll do that.
Since I redefined all the queues I have started to get this error whenever I deploy:
Mar 25 21:48:49 cose2e1 WMQIv210[8404]: (BROKER1)[1]BIP2070E: A problem was detected with MQSeries while issuing MQOPEN for MQSeries queue 'SYSTEM.BROKER.ADMIN.REPLY', MQSeries queue manager 'COS1'. MQCC=2, MQRC=2087. : BROKER1.agent: /build/S000_P/src/AdminAgent/ImbQueue.cpp: 206: ImbQueue::open: :
Mar 25 21:48:49 cose2e1 WMQIv210[8404]: (BROKER1)[1]BIP2068E: The broker was unable to put an internal configuration message to message queue 'SYSTEM.BROKER.ADMIN.REPLY'. : BROKER1.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 2397: ImbAdminAgent::receiveEGResponse: :
Plus I always have to do a complete Deploy with Force because the Control Center never thinks the previous deploy completed.
Any idea why? |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Mar 25, 2003 9:15 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I think there is some problem with the queue definitions. Since your broker is on different queue manager, I think the queue definitions(remote) will have to be changed.
I hope you have restarted your Broker after creating these queues and redefined the channels between Config Mgr and Broker queue managers.
Try this if you can,
0. Stop the broker.
1. Delete manually creaed queues (SYSTEM.BROKER.*) from your current queue manager.
2. Create another dummy broker with new queue manager on the same machine.
3. Backup SYSTEM.BROKER.* queue definition.
4. Run this script on the old queue manager.
5. delete the new broker and it's queue manager.
6. Restart machine if you can otherwise restart all components (Broker, queue manager and config mgr).
_________________
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 |
|
|
| pfaulkner |
| Posted: Wed Mar 26, 2003 11:18 am Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
Still got the same errors. I even tried deleting my broker completely, removing all the System.broker* queues. Removed broker from Config Mgr and then started over by creating a new broker (used a different name completely).
Added my new broker back into the Control Center and Redeployed.
Got same errors:
Mar 26 12:12:02 cose2e1 WMQIv210[25006]: (COS1BK)[1]BIP2070E: A problem was detected with MQSeries while issuing MQOPEN for MQSeries queue 'SYSTEM.BROKER.ADMIN.REPLY', MQSeries queue manager 'COS1'. MQCC=2, MQRC=2087. : COS1BK.agent: /build/S000_P/src/AdminAgent/ImbQueue.cpp: 206: ImbQueue::open: :
Mar 26 12:12:02 cose2e1 WMQIv210[25006]: (COS1BK)[1]BIP2068E: The broker was unable to put an internal configuration message to message queue 'SYSTEM.BROKER.ADMIN.REPLY'. : COS1BK.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 2606: ImbAdminAgent::sendDirectedResponseMessage: :
Mar 26 12:12:05 cose2e1 WMQIv210[25006]: (COS1BK)[1]BIP2070E: A problem was detected with MQSeries while issuing MQOPEN for MQSeries queue 'SYSTEM.BROKER.ADMIN.REPLY', MQSeries queue manager 'COS1'. MQCC=2, MQRC=2087. : COS1BK.agent: /build/S000_P/src/AdminAgent/ImbQueue.cpp: 206: ImbQueue::open: :
Mar 26 12:12:05 cose2e1 WMQIv210[25006]: (COS1BK)[1]BIP2068E: The broker was unable to put an internal configuration message to message queue 'SYSTEM.BROKER.ADMIN.REPLY'. : COS1BK.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 2606: ImbAdminAgent::sendDirectedResponseMessage: : |
|
| Back to top |
|
|
| pfaulkner |
| Posted: Wed Mar 26, 2003 1:24 pm Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
Solution.
I have named my xmitq 'destqmgr.xmitq' and apparantly SI requires the xmitq name to be 'destqmgr'.
Thanks for all the help. |
|
| Back to top |
|
|
|
|
