| Author |
Message
|
| vids |
 Posted: Thu Oct 21, 2004 3:44 pm Post subject: timeout error while deploying the bar |
 |
|
Acolyte
Joined: 24 Mar 2003
Posts: 68
Location: CA, USA
|
Hi
I have WBIMB 5.0.2, MQ 5.3 CSD04 running on Win 2k. Both configuration manager and broker are sharing the same Queue manager. When I try to deploy the bar file, I get the Timeout error.
I tried increasing the timeout period but didn't work. Right now I'm trying to deploy a test flow which is very small but I get the same error. I don't see any error related to this in event viewer.
Here is the log:
**********************************************************************************************
BIP2066E: Broker BRKR01 (UUID e18916bd-ff00-0000-0080-ef59bfad3ad9) was unable to retrieve an internal configuration response message for execution group 'RAD1' within the 1000 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.
Thanks |
|
| Back to top |
|
 |
| Nizam |
| Posted: Thu Oct 21, 2004 4:12 pm Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
Sounds silly but...Is the Broker Running?
Stop and Start the Broker and Deploy again.
Search this site for BIP2066E to get some help.
From WBIMB Tool Kit Help:
Message
Broker <insert_0> (UUID <insert_1>) was unable to retrieve an internal configuration response message for execution group '<insert_2>' within the <insert_3> second Configuration Timeout.
Explanation
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.
Response
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 Business Integration 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. |
|
| Back to top |
|
|
| siliconfish |
| Posted: Thu Oct 21, 2004 4:14 pm Post subject: |
|
|
Master
Joined: 12 Aug 2002
Posts: 203
Location: USA
|
Have u increased both of the ConfigurationTimeout and ConfigurationDelayTimeout.
_________________
siliconfish |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Oct 21, 2004 4:59 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
If it's a small message flow then you default timeout value should be fine. Few things that you can try,
1) Make sure the Broker is not deploying other message flow.
2) Try deploying message flow to different EG.
3) Delete and re-create the EG.
_________________
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 |
|
|
| vids |
| Posted: Thu Oct 21, 2004 7:15 pm Post subject: |
|
|
Acolyte
Joined: 24 Mar 2003
Posts: 68
Location: CA, USA
|
Yes my broker is running fine. I tried restarting the broker and redeploying the message flow. I didnt' have any problems before when I was deploying big message flows with the default timeout. Now I'm trying to deploy just one flow and I have increased the timeout too. I don't think I really need to change the timeout settings for a small message flow.
I started getting this problem after I recreated the execution group. I tried all the ways and then I dropped the broker and recreated the broker and execution group. It didn't work. Then I dropped broker, config manager, both broker and config mgr databases and recreated
everything. But I'm still having the same problem.
I see 2 dataflow engines running when I have only one execution group. After creating broker,I created new execution group and deleted the default one. Then I did the complete deploy which was successful. When I run mqsilist, it doesn't show any execution groups which is fine because
I have only one execution group and that too I have not deployed any message flows. But when I try to deploy the flow, before it times out, I see my execution group using mqsilist.
Is there anything else I can try??
Thanks |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Oct 21, 2004 10:12 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Can you install CSD4 on your machine? It seems you have a bad EG. Many people have posted this kind of problem before. If you do a search in this forum you might find related posts.
_________________
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 |
|
|
| PGoodhart |
| Posted: Fri Oct 22, 2004 6:05 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
The other possiblity is a bad bar file. Build a new one (you can use the same flows/sets) and try again. Make sure that you see the flows when you look at the bar file too. If there is an error in the flow, it won't always successfully add.
Here is what I am saying.
1. Add flow to bar file. This is like a compile.
Possible error flow error. Flow will not appear in the bar file. Deploying the bar file will have no effect.
2. Deploy bar file. This is like running the compiled bar.
Possible error flow error. Flow will not add to the execution group. This is like a runtime error.
Possible bad bar. Flow will not add to the execution group. This is like a bad compile.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| vids |
| Posted: Fri Oct 22, 2004 9:37 am Post subject: |
|
|
Acolyte
Joined: 24 Mar 2003
Posts: 68
Location: CA, USA
|
I'm able to deploy the flows now. The problem was with the java plugin nodes. Somehow after I recompliled all the java programs and restarted the broker it worked fine.
Thank you all..... |
|
| Back to top |
|
|
| RichJ |
| Posted: Tue Aug 02, 2005 2:09 am Post subject: |
|
|
Newbie
Joined: 02 Aug 2005
Posts: 1
|
How do you recompile the java plugins. What exactly do you mean? I'm assuming you're talking about the eclipse plugins...so how exactly do you recompile that?
Appreciate your help as I'm having similar problem |
|
| Back to top |
|
|
|
|
