| Author |
Message
|
| vam |
 Posted: Mon Jan 17, 2011 7:46 am Post subject: Flow not getting starrted after stoping |
 |
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
Hello All,
Few flows in our execution group have been stopped yesterday and they are not being started till now.
Tried to start as follows:
1) Tried to start using Toolkit (GUI).Not started
2) Tried using command line(mqsistartmsgflow).Not Started
3) Bounced the specific execution gropu(mqsireload). Not started.
Env Info:
WMB V6.1.0.3,HP-Unix
Log Info:
Jan 17 01:24:18 w21b1170 WebSphere Broker v6103[5601]: (BROKERA)BIP8099I: Retrieved NO message for Execution Group: Gen - : BROKERA
RC.agent: /build/S610_P/src/AdminAgent/ImbAdminAgent.cpp: 2446: ImbAdminAgent::receiveEGResponse: :
Jan 17 01:24:18 w21b1170 WebSphere Broker v6103[5601]: (BROKERA)BIP2066E[/b]: Broker 'BROKERA'(UUID '2b308880-2201-0000-0080-900d36b524d8') was unable to retrieve an internal configuration response message for execution group 'Gen' within the 360 second configuration timeout. : P
Need your help to resolve the prod issue. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jan 17, 2011 7:49 am Post subject: Re: Flow not getting starrted after stoping |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vam wrote: |
| Need your help to resolve the prod issue. |
Raise a PMR. We're not a support desk with an SLA & IBM can provide a more timely response to urgent issues.
Having said that, have you confirmed that:
- no "phantom" copies of these flows are running.
- Other flows in the EG are running?
- That the broker itself is running properly?
Also:
- Why were these flows stopped?
- Was the broker bounced at any point?
- Are there any other failed components anywhere (e.g. non-running channels)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Jan 17, 2011 10:37 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Moving this to the Broker forum...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| santnmq |
| Posted: Mon Jan 17, 2011 9:11 pm Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
Check if your system is not running short of resources, for example size of log directories , number of execution groups etc
if you find evrything OK, you can try to increase TIMEOUT value.... |
|
| Back to top |
|
|
| gag_nm |
| Posted: Mon Jan 17, 2011 11:26 pm Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 102
|
I am not an expert in WMB , but even i faced similar issues, i stopped broker,Broker Queue-manager and DB2 ,then started all components.
after that it was working fine. |
|
| Back to top |
|
|
| gag_nm |
| Posted: Mon Jan 17, 2011 11:28 pm Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 102
|
| stop and start even Configuration Manager |
|
| Back to top |
|
|
| santnmq |
| Posted: Mon Jan 17, 2011 11:35 pm Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
| Try all these options and evenif it's not working contact IBM support center. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 18, 2011 5:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santnmq wrote: |
| Try all these options and evenif it's not working contact IBM support center. |
I think the OP could have worked that out. Especially as I've already mentioned it. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
