| Author |
Message
|
| morpheus |
 Posted: Fri Sep 26, 2003 11:45 am Post subject: what is the best way to stop a broker? |
 |
|
Acolyte
Joined: 08 Mar 2003
Posts: 72
Location: Austin, TX
|
Hi guys
Does anybody know which is the best way to stop a queue manager that has a broker?
* stop the queue manager and not to worry about the broker
* stop the broker first and then queue manager
Which one is correct?
Thanks
-Morpheus |
|
| Back to top |
|
 |
| venkat kurra |
| Posted: Fri Sep 26, 2003 11:55 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
It is good idea to stop the broker first and then queue manager. Even if you stop the queue manager first,it should stop the broker and then queue manager.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| morpheus |
| Posted: Fri Sep 26, 2003 1:44 pm Post subject: Thank you |
|
|
Acolyte
Joined: 08 Mar 2003
Posts: 72
Location: Austin, TX
|
venkat,
Thank you for your reply. So what happens to the message that's in the queue when broker's shut down. Is it going to be processed later when everything restarted. I'm talking about non-persistent messages here. I want to make sure no message is lost. Does the queue manager stop receiving messages when we stop the broker. I want the queue manager to do that. How will I achieve that?
If you can suggest any source of information that'll also be helpful.
-Morpheus |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Sep 26, 2003 2:25 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
If you stop the broker, then there should be no reason for a QMGR to stop receiving messages. If you want to do that then may be PUT DISABLE your queue.
If they are non-persistent messages then if the QMGR is restarted, then you will not have them back. In that case you should either make the messages persistent, or should be affording to lose the messages. |
|
| Back to top |
|
|
| morpheus |
| Posted: Fri Sep 26, 2003 2:33 pm Post subject: Thank you |
|
|
Acolyte
Joined: 08 Mar 2003
Posts: 72
Location: Austin, TX
|
What if I stop the queue Manager? Does it stop the broker and stop receiving messages? or does it receive any messages between broker shutdown and QueueManager shutdown?
Thanx
-Morpheus |
|
| Back to top |
|
|
| morpheus |
| Posted: Fri Sep 26, 2003 2:40 pm Post subject: Thank you |
|
|
Acolyte
Joined: 08 Mar 2003
Posts: 72
Location: Austin, TX
|
What if I stop the queue Manager? Does it stop the broker and stop receiving messages? or does it receive any messages between broker shutdown and QueueManager shutdown?
Thanx
-Morpheus |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Sep 26, 2003 3:26 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
MQSeries is just that and the Broker is just an application that uses MQ.
As long as MQSeries is up, it can continue to accept messges, and applications that are connected can continue to GET messages. When you shut down MQ, it notifies any connected applications that is being terminated and they should gracefully end. This will include the broker, other connected applications and it will also include any channel MCAs running. This means that any 'well written' application will now cease to GET or PUT messages and will terminate. Or at least stop talking to MQ.
If you just terminate the broker, then all you have done is stopped a single MQ application. MQSeries will continue to function, as it always does.
How you co-ordinate those 2 actions is entirely down to how you want things to operate.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| morpheus |
| Posted: Mon Sep 29, 2003 10:42 am Post subject: Thank you |
|
|
Acolyte
Joined: 08 Mar 2003
Posts: 72
Location: Austin, TX
|
Thank you Eddie
I am now more clear.
-Morpheus |
|
| Back to top |
|
|
| mverh |
| Posted: Fri Oct 03, 2003 5:35 am Post subject: |
|
|
Voyager
Joined: 06 Mar 2002
Posts: 97
|
I have had this issue as well. Here is what you can do to ensure that no new messages arrive on broker input queues and all messages on broker input queues are pocessed prior to stopping a broker.
First you'll need to use MQ clusters. You create your broker input queues and expose them to your service requesters by having them join the cluster. Now when you need to stop the broker you would first suspend the broker qmgr from the cluster. This effectively stops any requester from sending any more messages to the broker queues. You then check your broker input queues to verify any messages sent prior to the suspension have been consumed. When all broker queues are empty you can stop the broker. When you start the broker you simply resume the qmgr into the cluster and now the broker input queus are advertised as being available again.
_________________
Marc Verhiel
IBM Canada Ltd. |
|
| Back to top |
|
|
|
|
