| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2080E |
« View previous topic :: View next topic » |
| Author |
Message
|
| pan_khandar |
 Posted: Thu Jul 11, 2002 6:51 am Post subject: BIP2080E |
 |
|
Novice
Joined: 21 Jun 2002
Posts: 17
|
Hi,
After deployment i am getting following error MSG.
BIP2080E: Execution Group PDM.XGRP1 failed to return an internal configuration Start message response within a 60 second time period. : DEV.BROKERA.agent: /build/S202_P/src/AdminAgent/ImbAdminAgent.cpp: 5525: ImbAdminAgent::getXMLResponse: :
What is the possible solution for this kind of weird behaviour?????
Thanks
pankaj
------------------------------------------------------------------------------ |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Jul 11, 2002 7:48 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Pankaj,
Do you see any errors in the event viewer or system log?
Usually this happens when,
- Deploy time for your message flow is greater than timeout period. You could use command mqsichangebroker to increase the timeout period.
- If your EG process is hanging while processing and it is not able to respond to your deploy request. This could be because of some looping in the messageflow, like in a while loop, the condition to come out of loop is not getting set.
Pl. recheck your message flow and see if this can be corrected.
To continue with the deploy operation, you could first stop the broker and then delete the message from input queue for this message flow. Restart the broker and then do a deploy for this Executiongroup.
_________________
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 |
|
|
| vmcgloin |
| Posted: Tue Jul 16, 2002 12:13 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Has anyone seen this error repeatedly after a broker is restarted (2.0.2)?
(We are not deploying.)
We have seen it a few times and normally a further restart is OK to sort it out. However now half of our production brokers have fallen over with this. 
Also, as soon as we try to start the brokers CPU use on the machine shoots up to 100% with DataFlowEngine processes being the culprit.
Any ideas where to look for a cause or solution?
Thanks,
Vicky |
|
| Back to top |
|
|
| MVO |
| Posted: Fri Nov 08, 2002 10:41 am Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
Hi,
I experienced the same problem with my production broker (Solaris 2.0.2 upd2). An extract of the system log (we have 2 exec groups) follows:
Nov 6 20:18:16 acpic-s181-e01 MQSIv202: [ID 702911 user.error] (cpicbroker)[6]BIP2060E: The broker has detected that the execution group execgroup1, process ID 26896, has terminated. : cpicbroker.agent: /build/S202_P/src/AdminAgent/ImbAdminAgent.cpp: 3548: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Nov 6 20:18:16 acpic-s181-e01 MQSIv202: [ID 702911 user.error] (cpicbroker)[8]BIP2060E: The broker has detected that the execution group acupies, process ID 27167, has terminated. : cpicbroker.agent: /build/S202_P/src/AdminAgent/ImbAdminAgent.cpp: 3548: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Any idea ?
Thanks |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Mon Nov 11, 2002 12:30 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
In our case this seems to be due to machine resource limits and we have to just check that brokers have started properly a miute or so after each restart. This is an extract of an email from IBM support that might help you.
| Quote: |
In general, if running multiple Brokers on the one box, and you are
starting the Brokers all at the same time, e.g. from a script, we
recommend that you stagger the start of each Broker allowing them
to start the EGs before starting the next Broker.
.
Also, in CSD03 for MQSI v2.0.2, there are two new environment variables
that allow you to configure the AdminAgent timeout values:
- MQSI_TIMEOUT_START : this allows you to modify the time which the
AdminAgent will wait for a response to the "start" message sent to the
EGs on Broker startup (default 60 seconds).
- MQSI_TIMEOUT : this allows you to modify the time which the
AdminAgent will wait for a response to a deploy request (default 300
seconds).
from 60 seconds to 120 seconds to see whether the system is just
responding slowly. |
Good luck,
Vicky |
|
| Back to top |
|
|
| MVO |
| Posted: Mon Nov 11, 2002 6:18 am Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
We have only one broker running on the server. It's hard to believe that we were running out of system resources. The strange thing was that the broker failed to start on the secondary node, HA switched it to the primary node and everything was OK. It happened a few times, always on the secondary node. I'm upgrading to WMQI 2.1 CSD03 next weekend, will try to use the 2 new environment variables. Since this is a HA environment, I will leave the broker up on one node while upgrading the second node. I'm just worried that when I switch over to node 2 - after the upgrade - so that I can upgrade node 1, the broker won't start.
\  |
|
| 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
|
|
|
|
