| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| execute group timeout error, help! |
« View previous topic :: View next topic » |
| Author |
Message
|
| steveneo |
 Posted: Thu May 03, 2007 10:57 pm Post subject: execute group timeout error, help! |
 |
|
Newbie
Joined: 13 Feb 2007
Posts: 3
|
My broker worked well before. but now it always report timeout error when i try to depoly message flow. The broker is in my local box, should not take long time to deploy (Before, it just take secondes). I tried create new broker, config mgr, queue, and use different database (Derby and DB2). I even tried reinstall broker, toolkit and MQ. The problem persist.  How can I trace this problem detail? The error message in event log is very rough. I am using window XP.
Any help is appreciated!
Here is detail error message:
| Code: |
BIP2066E: Broker BROKER108 (UUID 4131a950-1201-0000-0080-915c18e83822) was unable to retrieve an internal configuration response message for execution group '$SYS_mqsi' 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.
|
|
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Fri May 04, 2007 9:20 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Did you change the time out option by the by
try that, if that too doesn't work
Raise a PMR
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Bartez75 |
| Posted: Tue Sep 02, 2008 2:39 am Post subject: |
|
|
Voyager
Joined: 26 Oct 2006
Posts: 80
Location: Poland, Wroclaw
|
How to change this time out?
Ok. I found out.
mqsichangebroker BrokerName -g time |
|
| 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
|
|
|
|
