| Author |
Message
|
| Svp |
 Posted: Fri Mar 19, 2010 4:59 am Post subject: Stopping a Message Flow in ExecutionGroup |
 |
|
Apprentice
Joined: 18 Feb 2010
Posts: 40
|
Experts,
I have question.I am using WMB V7.0. I have a Execution Group TEST
in which three flows Flow A,Flow B and Flow C are running. If the Broker QMGR goes down, Broker also not available.
When the Broker QMGR comes up, the Broker starts. I found Execution Group and it flows A,B and C started to run automatically.
Is it possible to stop Flow A when the Broker QMGR comes up?(Not Manually)
Is it that I have to write a script to stop the FLOW A when the Broker QMGR recovers?
Any suggestions. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Mar 22, 2010 10:31 am Post subject: Re: Stopping a Message Flow |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Hi SVP!
Great question. One out-of-the-box way to do it would be to have another flow in your EG (say Flow D) put a message on a queue that has a trigger to start a script. Whenever EG comes up from an outage, Flow D starts, puts the message on the queue, queue depth triggers a script that stops Flow A. The Flow D could be optionally triggered by a FileInput node, when a file exists on the OS. On system boot, start-up script could write this file so Flow D is triggered.
Let me know if this is unclear, and I will elaborate on it. But pretty straight-forward.
HTH
Sirlancelotlinc
Rorqual qualified. |
|
| Back to top |
|
|
| Svp |
| Posted: Mon Mar 22, 2010 12:04 pm Post subject: |
|
|
Apprentice
Joined: 18 Feb 2010
Posts: 40
|
| I can also use JAVA COMPUTE node in Flow D which uses CMP API to stop the Flow D. |
|
| Back to top |
|
|
| Svp |
| Posted: Mon Mar 22, 2010 12:05 pm Post subject: |
|
|
Apprentice
Joined: 18 Feb 2010
Posts: 40
|
Sorry...
I can also use JAVA COMPUTE node in Flow D which uses CMP API to stop the Flow A. |
|
| Back to top |
|
|
| hallmark |
| Posted: Wed Mar 24, 2010 6:19 am Post subject: |
|
|
Voyager
Joined: 10 Mar 2005
Posts: 76
|
Without giving it too much thought perhaps it is possible for an MQ Service which effectively runs a scripted command to stop the message flow in question.
That's probably closer to stopping said flow before it processes anything (though not guaranteed I guess). The problem with flow D doing it is that assumes flows have already started by that point and presumably there is a reason you wish to stop a flow for processing reasons. |
|
| Back to top |
|
|
| bloomy |
| Posted: Thu Mar 25, 2010 1:27 pm Post subject: |
|
|
Acolyte
Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA
|
| Quote: |
| That's probably closer to stopping said flow before it processes anything (though not guaranteed I guess). The problem with flow D doing it is that assumes flows have already started by that point and presumably there is a reason you wish to stop a flow for processing reasons. |
I agree with this, if the Flow D is used to stop A, we cannot assure that Flow D starts before Flow A and by the time Flow D processes it's messages(message to stop the flow A) the Flow A will be running and process its messages which you do not want to happen I guess. I wonder if there is any setting on the flows that we can set to say to the broker not to start a particular flow after the broker restart automatically. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Mar 25, 2010 2:26 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the flow uses an MQInput node, after you start the Queue Manager, but before you start the Broker, Get Inhibit the Input queue.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
