| Author |
Message
|
| paustin_ours |
 Posted: Mon Aug 02, 2004 2:53 pm Post subject: Broker unable to retrieve internal config response |
 |
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
I am trying to deploy a message flow on my default execution group, I get the following error.
BIP2066E: Broker MQSI_SAMPLE_BROKER (UUID a5923832-dd00-0000-0080-ab4b84e10d89) was unable to retrieve an internal configuration response message for execution group 'default' within the 360 second Configuration Timeout.
Does it have anything to do with the log file size??the q.mngr is on circular logging.
I have like 7 message sets and 4 or 5 message flows on the memory but i am just tryin to deploy one of that, i assigned a message set to the broker and a flow to the default execution group. Is this a memory problem? If so how shud i go about it? need help. |
|
| Back to top |
|
 |
| CoolDude |
| Posted: Mon Aug 02, 2004 5:49 pm Post subject: |
|
|
Apprentice
Joined: 17 Jan 2004
Posts: 39
|
Did you check the syslogs or the event logs. What do they say? Often this problem is resolved by recycling the configuration manager. We need to recycle all the components on that box.
Also clear the shared memory.
Note : This error may be due to some communication error to Message Repository or Configuration manager database.
Please check the logs.
Thanks.
_________________
Correct Me from Wrong  . If i am correct Appreciate Me  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 03, 2004 5:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You shouldn't recycle the configuration manager until you understand the problem.
First off, check the queue managers that connect your broker with your configuration manager, and ensure that the channels between the two are running. If the broker and configuration manager are sharing a queue manager, then check for SYSTEM.BROKER.* queues that have a positive queue depth.
Then check to see if your broker is running, and the configuration manager is running.
Third, what version are you running and on what platform?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| waugh |
| Posted: Tue Aug 03, 2004 5:32 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
I would do the following:
1) right click on domain connection and do cancel deployment.
2) mqsistop configmgr
3) clear messages from SYSTEM.BROKER.ADMIN.QUEUE and SYSTEM.BROKER.ADMIN.REPLY
4) START configuration manager.
mqsistart configmgr
check logs when you issue the mqsistart configmgr command to see if the configuration manager coming up properly. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Tue Aug 03, 2004 8:00 am Post subject: Its Fixed |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
Thanks Waugh/Jeff,
I did try the steps you told me waugh,it worked. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Tue Aug 03, 2004 8:05 am Post subject: Oops i forgot to thank cooldude |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
|
| Back to top |
|
|
|
|
