| Author |
Message
|
| dkiu |
 Posted: Sun Jan 26, 2014 2:45 am Post subject: Identifying looping Message Flow inside an Execution Group |
 |
|
Apprentice
Joined: 28 Feb 2013
Posts: 25
|
Hi,
I want to know which particular message flow is causing a loop within Execution Group. I can identify looping EG by using Top command in Linux environment but not sure how to catch the looping message flow amidst too many flows. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sun Jan 26, 2014 9:58 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Stop all the flows in the EG
Reload it
Start each flow one by one and observe.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Jan 26, 2014 11:02 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Enable statistics (for the EG) in MBX. View statistics in MBX,
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| Esa |
| Posted: Sun Jan 26, 2014 10:40 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| smdavies99 wrote: |
Stop all the flows in the EG
|
The flow that doesn't stop is the one that is looping. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Jan 26, 2014 11:04 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Esa wrote: |
| smdavies99 wrote: |
Stop all the flows in the EG
|
The flow that doesn't stop is the one that is looping. |
I know that. That was why the next step was to 'reload it' i.e. Reload the EG. That way it restarts with everything stopped.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 27, 2014 5:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
| Enable statistics (for the EG) in MBX. View statistics in MBX, |
Faster and less disruptive.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dkiu |
| Posted: Mon Jan 27, 2014 7:39 am Post subject: |
|
|
Apprentice
Joined: 28 Feb 2013
Posts: 25
|
Thanks ! ...I will try and observe this.
On the other hand , I thought there might be some MQSC command to check this at EG level. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 27, 2014 8:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dkiu wrote: |
| I thought there might be some MQSC command to check this at EG level. |
mqsifindloopingflow? Afraid not  
Note that we're suggesting statistics at an EG level, not a broker level, so it's almost what you're talking about.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
