| Author |
Message
|
| harishre |
 Posted: Wed Jun 25, 2008 7:43 am Post subject: BIP 2066 error while deploying |
 |
|
Apprentice
Joined: 29 May 2008
Posts: 27
|
Hi All,
I have some new problem with deployment today..... 
I have successfully migrated a broker from 2.1 to 6.0 then I have created an EG for that.
everything went fine till here, but when i tried to deploy the flows in to this EG, I am getting the following error.
| Quote: |
BIP2066E: Broker TEST_BROKER(UUID 7e46b0a5-1a01-0000-0080-fd44fda315bf) was unable to retrieve an internal configuration response message for execution group 'TEST_EG' 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. |
I even tried to deploy using mqsideploy but got the following error
| Quote: |
| BIP1100E: Broker TEST_BROKER had not responded before the timeout occurred. |
I have incresed the timeout period using the command mqsichangebroker and tried to redeploy but got the same error......
could anyone please tell me what may be the error... |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jun 25, 2008 8:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
communications problems between broker qmgr and configmgr qmgr. Broker not running, not picking up msgs from EG config queues etc...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| harishre |
| Posted: Wed Jun 25, 2008 8:29 am Post subject: |
|
|
Apprentice
Joined: 29 May 2008
Posts: 27
|
| fjb_saper wrote: |
| communications problems between broker qmgr and configmgr qmgr. Broker not running, |
I have started channels between broker and configuration manager.. they are up and running....
Broker is running, cuz if i give ps -ef|grep <broker name>
i could see the following processes running
1) biphttplistener
2) bipservice
3) bipbroker
| Quote: |
| not picking up msgs from EG config queues etc.. |
if this is the reason what has to be done... plz tell me.... |
|
| Back to top |
|
|
| harishre |
| Posted: Wed Jun 25, 2008 8:33 am Post subject: |
|
|
Apprentice
Joined: 29 May 2008
Posts: 27
|
for your information.......
there are three processes are running for biphttplistener ....
could this be the problem????? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 25, 2008 10:12 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| harishre wrote: |
| fjb_saper wrote: |
| communications problems between broker qmgr and configmgr qmgr. Broker not running, |
I have started channels between broker and configuration manager.. they are up and running....
Broker is running, cuz if i give ps -ef|grep <broker name>
i could see the following processes running
1) biphttplistener
2) bipservice
3) bipbroker
| Quote: |
| not picking up msgs from EG config queues etc.. |
if this is the reason what has to be done... plz tell me.... |
Having your 3 mentioned 'bip*' processes running does not mean that the broker can attach to its database. So it does not mean broker running....
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| harishre |
| Posted: Wed Jun 25, 2008 11:35 pm Post subject: |
|
|
Apprentice
Joined: 29 May 2008
Posts: 27
|
| Quote: |
| Having your 3 mentioned 'bip*' processes running does not mean that the broker can attach to its database. So it does not mean broker running.... |
so could you please tell me how to check whether the broker is running or not....
When I have restarted the broker using mqsistart, i got the successful completion command prompt..... from that, i said that broker is running....
is there any other way to find whether broker is really running or not????? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 26, 2008 1:34 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| harishre wrote: |
| Quote: |
| Having your 3 mentioned 'bip*' processes running does not mean that the broker can attach to its database. So it does not mean broker running.... |
so could you please tell me how to check whether the broker is running or not....
When I have restarted the broker using mqsistart, i got the successful completion command prompt..... from that, i said that broker is running....
is there any other way to find whether broker is really running or not????? |
As the message says when you get the prompt, you need to check the logs before you can say whether the broker is running without problems or not.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
