| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2080???? |
« View previous topic :: View next topic » |
| Author |
Message
|
| TonyD |
 Posted: Sun Nov 02, 2008 6:09 pm Post subject: BIP2080???? |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| Code: |
Nov 3 14:46:12 eqcigs11 WebSphere Broker v6006[7792]: (SIT_BKR01)[-1243507008]BIP2080E: Execution Group default failed to return an internal configuration Start message response within a 60 second time period. :SIT_BKR01.agent: /build/S600_P/src/AdminAgent/ImbAdminAgent.cpp: 7161: ImbAdminAgent::getXMLResponse: :
|
One of my brokers is returning this annoying message for two of its four execution groups. One eg has no flows deployed (default), the other has four flows, all of which are shown as stopped and cannot be started. SYSTEM.BROKER.EXECUTIONGROUP.QUEUE has two messages on it that are not being picked up, leading to the above BIP message which appears every 130 seconds for the two egs. The other two egs are fine.
I have seen this message many times before on different brokers but have never worked out how to resolve it, short of restarting the broker, and often that does not fix the problem.
Does anyone know what to do to fix the problem? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Nov 02, 2008 7:30 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Did you try and reload the eg? IIRC there is line command for this. Look it up under mqsi*. If that does not work you may have to recycle the broker... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqpaul |
| Posted: Tue Nov 04, 2008 3:36 am Post subject: Re: BIP2080???? |
|
|
Acolyte
Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK
|
| TonyD wrote: |
...
| Code: |
BIP2080E: Execution Group default failed to return an internal configuration Start message response within a 60 second time period. |
...
One of my brokers is returning this annoying message for two of its four execution groups.
...
I have seen this message many times before on different brokers but have never worked out how to resolve it, short of restarting the broker, and often that does not fix the problem.
Does anyone know what to do to fix the problem? |
The trouble is that BIP2080E is a symptom, not a disease. It says the configuration manager sent a Start message but the receiving EG didn't respond. The disease is whatever stopped the EG; that could be lots of things - out of memory, out of disk, a rogue node killing the EG, etc.
The places to look are the EG's logs and traces (use
to get the trace data, since that reads the files directly, not via the unresponsive EG) and the various error files under /var/mqsi, such as the JVM stdout and FFDC files.
_________________
Paul |
|
| Back to top |
|
|
| TonyD |
| Posted: Tue Nov 04, 2008 7:05 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
Thanks for the comments.
I have pretty much already checked as suggested. I have one eg in particular that contains one flow which is a 'utility' email flow that has been used for a long time. At the moment this flow is shown as stopped. It cannot be removed from the eg since the deploy request messages are not being read. It also cannot be started
I have dealt with similar cases in the past where the egs had zzombie clones lurking. However in this case the broker database, mqsilist, the toolkit and the CM Proxy exerciser all show only the four expected egs. The stderr and stdout files show only 'ExecutionGroup started' entries ... nothing else.
Any further ideas appreciated. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 04, 2008 10:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| TonyD wrote: |
Thanks for the comments.
I have pretty much already checked as suggested. I have one eg in particular that contains one flow which is a 'utility' email flow that has been used for a long time. At the moment this flow is shown as stopped. It cannot be removed from the eg since the deploy request messages are not being read. It also cannot be started
I have dealt with similar cases in the past where the egs had zzombie clones lurking. However in this case the broker database, mqsilist, the toolkit and the CM Proxy exerciser all show only the four expected egs. The stderr and stdout files show only 'ExecutionGroup started' entries ... nothing else.
Any further ideas appreciated. |
Verify if there is a message stuck on any of the system.broker queues or on any xmitq on the configmgr's qmgr or the broker's qmgr.
Are all the channels reporting back as working correctly (configmgr to broker and broker to configmgr). Do you still have a default path from one to the other and vice versa?
If all this looks fine, stop the current deployment and redeploy.
Enjoy
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
