| Author |
Message
|
| eai143 |
 Posted: Tue Sep 12, 2006 11:13 pm Post subject: Broker and Execution Groups not running. |
 |
|
Apprentice
Joined: 16 Aug 2006
Posts: 28
|
Hi,
There are two execution groups in my broker.
As soon as Iam starting the broker, the dataflow engines are consuming almost 96% of CPU. And the broker and execution groups are not starting.
Its giving the error as follows:
( WBRK_BROKER ) Execution Group Default failed to return an internal configuration Start message response within a 60 second time period.
The internal configuration message response could not be retrieved. The Execution Group therefore failed to move to the state described by the internal configuration message.
Investigate why the Execution Group internal configuration message response was not returned within the allowed time period by reviewing messages issued to the system log. Additionally, you can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationDelayTimeout. This will not resolve any underlying problem with a deployed configuration message, but can be used to reduce the response turnaround time or allow for large and complex deployments. Resolve any problems described in the system log. This 'internal configuration' operation will be retried automatically, if you continue to see this message you should investigate the reason for the Execution Groups failure to respond.
How can this be solved.
Thanks in advance. |
|
| Back to top |
|
 |
| jbanoop |
| Posted: Wed Sep 13, 2006 12:23 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
has it something to do with some flow deployed on the execution groups which is going in some infinite loop ?
whta is the platform and fix pack level and version you are using ?
Anoop |
|
| Back to top |
|
|
| eai143 |
| Posted: Wed Sep 13, 2006 1:04 am Post subject: |
|
|
Apprentice
Joined: 16 Aug 2006
Posts: 28
|
It worked nicely till last week.The broker service went into stopping state and I restarted the system.From then onwards Iam getting this problem.
Iam working with MB5.0 on windows.
Thanks. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Wed Sep 13, 2006 1:33 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
maybe you might have corrupted your broker db tables during that forced shutdown .. I am just guessing.
try killing the broker db (db2stop force if you are using db2), stop the broker,config mgr n the agent controller and then start db2 or equivalent and then the broker.
see if you get any database access error on the event log when the broker tries to start..
Anoop |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 13, 2006 1:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| jbanoop wrote: |
| has it something to do with some flow deployed on the execution groups which is going in some infinite loop ? |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| eai143 |
| Posted: Wed Sep 13, 2006 3:14 am Post subject: |
|
|
Apprentice
Joined: 16 Aug 2006
Posts: 28
|
Anoop, I did what u told,But still getting the same problem.
There are no infinite loops in the code.And I deleted the flows from the execution groups,but still showing the same error. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Wed Sep 13, 2006 3:42 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
how exactly did u delete the flows from the execution groups if configuration messages to the execution group were timing out inside ?
did u try mqsireload on the execution groups ?
kill all the bip processes as well as the dataflow engine processes close the toolkit and then clear the input queue(s) used by the "deployed" flows (the ones which were supposed to b deployed to the execution grp when the prob started). then start the broker.
Monitor the event log/syslog for ny errors during broker/config mgr process.
post any errors you get.
If startup is clean then i am out of ideas 
Anoop |
|
| Back to top |
|
|
| eai143 |
| Posted: Wed Sep 13, 2006 4:32 am Post subject: |
|
|
Apprentice
Joined: 16 Aug 2006
Posts: 28
|
I stopped the broker and deleted the flows from the execution group.
I killed all the bipprocesses and then started the broker, but same problem. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 13, 2006 4:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can *not* delete the flows from the Execution Group when the broker is STOPPED.
Kill all the bip processes.
Mark all queues that are being read by an MQInput node as "GET DISABLED".
Start the broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
