| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Could not stop broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeevan |
 Posted: Mon Sep 05, 2011 1:42 pm Post subject: Could not stop broker |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I could not stop one of my two brokers in my test system. The task itelf is not so critical as this is a test system but I need to understand why it behaves this way.
Initially both broker were running, I issued command to stop the one which did not stop. I checked, but it was not stopping. I combined the command to stop the queue manager as well but it failed.
But when I issued the command to stop the other broker, it worked as expected.
what could be a reason?
where can check the log ( does it have log at all for system command like mqsistop etc?)
C:\Program Files\IBM\MQSI\7.0>MQSILIST
BIP1284I: Broker 'TESTBRK' on queue manager 'BROKERQM' is running.
BIP1285I: Broker 'TESTBROKER' on queue manager 'TEST' is stopped.
BIP8071I: Successful command completion.
C:\Program Files\IBM\MQSI\7.0>mqsistop TESTBRK
BIP8019E: Component stopped.
A previous command was issued to stop this component or it has never been started.
This component may be started, changed or deleted.
C:\Program Files\IBM\MQSI\7.0> |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Sep 05, 2011 4:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If a broker does not stop after issuing the mqsistop -i command, I start by killing off the corresponding execution group processes. Usually that does it. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Sep 05, 2011 5:27 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| fjb_saper wrote: |
| If a broker does not stop after issuing the mqsistop -i command, I start by killing off the corresponding execution group processes. Usually that does it. |
Very interesting. Even the broker was not connected to tool kit. I connected broker with tool kit and then killed the eg. When I killed the EG, the broker stopped automatically. I do not have to reissue the command again.
I think the previous command was hung or was pending and now got activated. I do not know how though.
Thanks a lot
Last edited by jeevan on Mon Sep 05, 2011 5:32 pm; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 05, 2011 7:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jeevan wrote: |
| fjb_saper wrote: |
| If a broker does not stop after issuing the mqsistop -i command, I start by killing off the corresponding execution group processes. Usually that does it. |
Very interesting. Even the broker was not connected to tool kit. I connected broker with tool kit and then killed the eg. When I killed the EG, the broker stopped automatically. I do not have to reissue the command again.
I think the previous command was hung or was pending and now got activated. I do not know how though.
Thanks a lot |
If one of the flows goes into a loop you usually will have to kill the eg before the broker will process other commands concerning that eg.
Have fun
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
