| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| execution group error |
« View previous topic :: View next topic » |
| Author |
Message
|
| rkford11 |
 Posted: Tue Nov 02, 2004 2:26 pm Post subject: execution group error |
 |
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
i am getting the following error and unable to deploy or start the message flows.
BIP2066E: Broker ABCD (UUID 93def840-ff00-0000-0080-fd7d4981b447) was unable to retrieve an internal configuration response message for execution group 'default' within the 360 second Configuration Timeout.
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.
Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere MQ log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if you are unable to resolve the problem.
What would be the best solution? |
|
| Back to top |
|
 |
| Nizam |
| Posted: Tue Nov 02, 2004 2:42 pm Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
| I would increase the timeout period and try to deploy a simple flow. |
|
| Back to top |
|
|
| OmPat |
| Posted: Tue Nov 02, 2004 2:51 pm Post subject: |
|
|
Apprentice
Joined: 20 Jul 2004
Posts: 33
Location: Charlotte
|
your flow might be involved in a looping process... I would do a check on the resources consumed by the execution group.... If everyting else fails i will do a kill -9 on the execution group... MQSI would automatically restart the exectuion group with a different process id... after it is done do a deploy to that execution group... Hope this helps u....
Thanks,
~Om
_________________
IBM Certified WMQ V5.3 System Administrator
IBM Certified WMQ V5.3 Solutions Designer
Brainbench Certified MQ Expert
IBM Certified WMQI V2.1 Solutions Expert
IBM Certified WMQI V2.1 Specialist |
|
| Back to top |
|
|
| rkford11 |
| Posted: Tue Nov 02, 2004 3:05 pm Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| OmPat wrote: |
your flow might be involved in a looping process... I would do a check on the resources consumed by the execution group.... If everyting else fails i will do a kill -9 on the execution group... MQSI would automatically restart the exectuion group with a different process id... after it is done do a deploy to that execution group... Hope this helps u....
Thanks,
~Om |
how do i kill the process or increase the timeout period on the execution group?
and this was another error continued
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker ABCD.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker ABCD was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker ABCD. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.
Thanks |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Nov 03, 2004 12:05 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
It'd be better to disable the input queue for MQGET before killing the EG process. IF your message is looping it will rollback to your input queue if you are processing the message in UOW.
I think you don't need to increase the time-out value.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
