| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Getting error while deploying the message flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| chris boehnke |
 Posted: Wed May 09, 2007 12:23 pm Post subject: Getting error while deploying the message flow |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
BIP2066E: Broker MBMIMSG02BK1 (UUID e8f96d39-0e01-0000-0080-8be714c01c81) was unable to retrieve an internal configuration response message for execution group 'Test' 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 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, mqsideploy command or Config Manager Proxy. 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.
Please suggest me
Thanks.
Chris |
|
| Back to top |
|
 |
| sourdas2 |
| Posted: Thu May 10, 2007 12:13 am Post subject: |
|
|
Voyager
Joined: 21 Apr 2006
Posts: 90
Location: Kolkata,India
|
Is your BROKER and BROKER Queuemanager started. Is the communication link between your broker qmgr and configmgr qmgr up and running.
Run 'mqsilist <BROKER>' to justify the connection between database and broker.
_________________
Thanks and Warm Regards
Sourav |
|
| Back to top |
|
|
| pathipati |
| Posted: Sat May 12, 2007 9:19 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| sourdas2 wrote: |
| Is your BROKER and BROKER Queuemanager started. Is the communication link between your broker qmgr and configmgr qmgr up and running. |
If this is the problem then I don't think even Chris can go that far where he can see above exception. |
|
| 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
|
|
|
|
