| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Stopping broker forcefully using "-i" flag with mq |
« View previous topic :: View next topic » |
| Author |
Message
|
| amitkothari18 |
 Posted: Fri May 27, 2011 5:19 pm Post subject: Stopping broker forcefully using "-i" flag with mq |
 |
|
Novice
Joined: 12 Feb 2011
Posts: 24
|
Hi All,
I have a very basic questions:
Is it ok to everytime stop a broker forcefully using "mqsistop BrokerA -i" command or it can have some adverse effects on regular use?
What to do if the broker does not stop normally even after 30mins. We have a broker with 6 execution grps, 5 of them stop after 5-10mins but one of the execution grp does not stop even after 30 mins of executing the normal "mqsistop" command. We make sure that there are no messages being processed before executing the "mqsistop" command and still this execution group does not stop. The only visible difference is we see high Paging memory utilization by this exection group.
WMBv.6.1.0.8
WMQv.7.0.1
WTXv.8.2.0.5
AIX5.x
Any responses are greatly appreciated.... |
|
| Back to top |
|
 |
| bsiggers |
| Posted: Fri May 27, 2011 8:07 pm Post subject: |
|
|
Acolyte
Joined: 09 Dec 2010
Posts: 53
Location: Vancouver, BC
|
Hmm, depending on what your execution groups are doing, you might want to try killing the offending execution group process directly (via unix kill command against the EG PID), if you can somehow ensure that the flow in fact is not actually doing anything useful.
I've seen this happen before, normally in the cases where the EG or one of the flows within the EG are misbehaving. Better to check there for the root cause of the issue.
Would be interested in what the experts have to say, as this is a relatively common issue in my experience. |
|
| Back to top |
|
|
| bsiggers |
| Posted: Fri May 27, 2011 8:09 pm Post subject: |
|
|
Acolyte
Joined: 09 Dec 2010
Posts: 53
Location: Vancouver, BC
|
| Going back to your original question, stopping the broker with '-i' is probably not a good idea. Depending on your use cases, you could lose messages, or end up in some kind of weird state. You're better off in the long term trying to isolate the real cause of the issue and correcting it. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat May 28, 2011 5:39 am Post subject: Re: Stopping broker forcefully using "-i" flag wit |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| amitkothari18 wrote: |
| one of the execution grp does not stop even after 30 mins of executing the normal "mqsistop" command. We make sure that there are no messages being processed before executing the "mqsistop" command and still this execution group does not stop. |
If this happened more than once, I'd be very concerned about what one of the flows is doing in there. If the flow's not responding to a stop command, not processing any message and has high paging rates then that's a receipe for bad things to happen.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| amitkothari18 |
| Posted: Wed Jun 01, 2011 1:05 pm Post subject: Thanks for your responses!! |
|
|
Novice
Joined: 12 Feb 2011
Posts: 24
|
| Thanks everyone for your responses...we are going to diagnose further into the issue why the flows are not stopping properly... |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
