Author |
Message
|
bkiran2020 |
Posted: Thu Jul 25, 2013 6:46 pm Post subject: Flow process |
|
|
 Master
Joined: 20 Jan 2011 Posts: 243 Location: US
|
If I want to check the which flow process is connected to the queue.
Iam only able to find the EG process only.
Is there any other alternative to find which flow process is connected to the queue. |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Jul 25, 2013 9:05 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Flows don't have a 'Process' in the conventional sense. They have a thread( Or more than one if active and/or additiional instances configured)
The MQExplorer properties display can help you find out what queues are used by the individual flow.
Otherwise, you can use the tried and tested method of stopping each flow in the EG in turn and seeing which one is the guilty party. _________________ 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.
Last edited by smdavies99 on Fri Jul 26, 2013 12:41 am; edited 1 time in total |
|
Back to top |
|
 |
bkiran2020 |
Posted: Thu Jul 25, 2013 11:58 pm Post subject: |
|
|
 Master
Joined: 20 Jan 2011 Posts: 243 Location: US
|
smdavies99 wrote: |
Flows don't have a 'Process' in the conventional sense. They have a thread( Or more than one if activa and/or additiional instances configured)
The MQExplorer properties display can help you find out what queues are used by the individual flow.
Otherwose, you can use the tried and tested method of stopping each flow in the EG in turn and seeing which one in the guilty party. |
Below statement are correct or not
Depends on requirement. Each EG is a process (u can check DataFlowEngine.exe in task manager processes). Now if you want to spread out your load, then you can go for multiple EG. Else you can go for additional instances. Again one more point is that in a single EG, you cant go more than 255 instances of a single flow. |
|
Back to top |
|
 |
vishnurajnr |
Posted: Fri Jul 26, 2013 4:31 am Post subject: |
|
|
 Centurion
Joined: 08 Aug 2011 Posts: 134 Location: Trivandrum
|
|
Back to top |
|
 |
mqjeff |
Posted: Fri Jul 26, 2013 5:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You should still *know* which flows will be reading from which queues, without having to figure it out. The flows should be documented. The flows should follow naming conventions. The queues should be documented, the queues should follow naming conventions.
If you have to programatically figure out which flow is reading which queue more than TWICE, then you are not doing the right thing. |
|
Back to top |
|
 |
|