| Author |
Message
|
| mca |
 Posted: Thu Dec 20, 2012 9:04 pm Post subject: force stop a message flow in broker |
 |
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
i am trying to stop a message flow in Broker. It does not stop. I tried to look for force stop option, but i don't see it.
Isn't there a force stop option like "-i" to immediately stop Queue Manager |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Dec 21, 2012 8:12 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Dec 21, 2012 8:52 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
kill -9
|
How does that command work on Windows?
Using 'kill -9' also requires that you know what processes to stop.
Where in the OP does it say that the user ID is 'mqm'?
_________________
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 |
|
|
| lancelotlinc |
| Posted: Fri Dec 21, 2012 8:57 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smdavies99 wrote: |
| lancelotlinc wrote: |
kill -9
|
How does that command work on Windows?
Using 'kill -9' also requires that you know what processes to stop.
Where in the OP does it say that the user ID is 'mqm'? |
All good points. More info is needed in the post to be conclusive.
With Windows, you can right click from the Process Manager.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mca |
| Posted: Fri Dec 21, 2012 11:57 am Post subject: |
|
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
My flow is running on Linux. I tried to grep the Process ID using ps -ef|grep msgflowName and it gives me dataflowengine processid. I do kill -9 <pid>.
It still doesn't work. I need the broker to be running, but just stop this running flow. Any other options? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Dec 21, 2012 12:18 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mca wrote: |
My flow is running on Linux. I tried to grep the Process ID using ps -ef|grep msgflowName and it gives me dataflowengine processid. I do kill -9 <pid>.
It still doesn't work. I need the broker to be running, but just stop this running flow. Any other options? |
Don't use mqm as your Broker service Id, then you wont have the problem to begin with.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mca |
| Posted: Fri Dec 21, 2012 12:23 pm Post subject: |
|
|
Disciple
Joined: 09 Mar 2005
Posts: 196
|
| mqsireload solved the issue. Thanks for all your help. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 21, 2012 12:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Don't use mqm as your Broker service Id, then you wont have the problem to begin with. |
How do you know that's the OP's problem? There are many reasons a flow won't stop. Badly written ESQL is the most common reason in my experience and no choice of service id will prevent this.
And before you start about build processes, testing and how this should never happen, there's nothing to indicate this is a Prod environment. Just that the broker needs to keep running, which could easily be a busy shared Dev environment.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Dec 21, 2012 1:04 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Vitor wrote: |
How do you know that's the OP's problem? There are many reasons a flow won't stop. Badly written ESQL is the most common reason in my experience and no choice of service id will prevent this.
And before you start about build processes, testing and how this should never happen, there's nothing to indicate this is a Prod environment. Just that the broker needs to keep running, which could easily be a busy shared Dev environment. |
Well Said Sir Vitor.
If you have never coded a while/for loop and forgot to increment the counter then you have obviously never done much programming. After 40+ years of programming even I am sad to say make the occassional mistake when coding.
Then you see the CPU load go to 100% and then you realise how silly/stupid you have been have egg on you face.
_________________
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 |
|
|
|
|
