| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Power Down |
« View previous topic :: View next topic » |
| Author |
Message
|
| fryit99 |
 Posted: Wed Aug 24, 2005 12:58 am Post subject: Power Down |
 |
|
Newbie
Joined: 24 Aug 2005
Posts: 1
|
We have a power down this weekend, and nobody appears able to tell me proper shutdown procedure for MQ Series.
Arrangements have been made to minimise traffic to/from the building, but is it best to shutdown MQSeries first, last or somwhere in between? |
|
| Back to top |
|
 |
| hopsala |
| Posted: Wed Aug 24, 2005 2:55 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Assuming you are NOT using MQ Clusters or some hardware cluster, there is no real shutdown procedure, simply "endmqm QMGR". If you are using clusters, post it.
However, if this is a risky shutdown, and you have the time and patience for it, you'd probably want to clear all the queues before shutting down:
1. Stop all receiver channels, thus preventing any new messages from remote qmgrs.
2. Wait for the applications to read all queue content and send all possible replies. When all application queues are empty shutdown the applications.
3. Wait until all sender channels empty all XMIT queues.
4. stop the qmgr.
All this is pure logic, nothing special... |
|
| Back to top |
|
|
| maxis |
| Posted: Thu Aug 25, 2005 3:50 am Post subject: |
|
|
Centurion
Joined: 25 Jun 2002
Posts: 144
|
what would be your recommend if 2 queuemangers are in cluster ? ...
cheers
m |
|
| Back to top |
|
|
| hopsala |
| Posted: Thu Aug 25, 2005 4:51 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Theoretically, one should be able to do something like this:
1. SUSPEND QMGR
2. Wait for all appls to empty their qs and shut them down.
3. Wait for SYSTEM.CLUSTER.TRANSMIT.QUEUE to empty.
4. Stop the QM
However, suspending the QM does not mean that necessarily no messages will arrive (see post http://www.mqseries.net/phpBB2/viewtopic.php?t=23672&highlight=suspend+cluster). Not only that, but i'm not entirely sure SUSPEND QMGR does not also stop outgoing traffic - I think it doesn't, and if so we're in the clear - but maybe someone around the forum has tried it and knows...
In any event, maybe you could try this one:
1. SUSPEND QMGR
2. Stop CLUSRCVR channel, truely preventing any new messages to arrive from remote qmgrs, while the repository will see that you're down and let all the other qms know.
2. Wait for all appls to empty their qs and shut them down.
3. Wait for SYSTEM.CLUSTER.TRANSMIT.QUEUE to empty.
4. Stop the QM
This should work, but I haven't tried it - and when clusters are concerned don't assume anything without experimenting with it first. There's a good chance that once you stop the CLUSRCVR channels, the applications will have problems sending - since either the shared queues table will expire, the QM will decide there's a general problem with the cluster and refuse to send, or if the appls will try sending to shared queues they haven't sent to before, these queues are unknown and the qm has no way of asking the repository... Your appls might start getting 2085 etc.
If you truely need this, you definitely should make some experiments with this (and post your conclusions!), or wait for other people to posts their suggestions, maybe they have a better idea or some answers to these questions.
(p.s if all else fails, one can always stop all receivers and backup application queues to text files and use saveqmgr, or even make a physical backup of the entire qm) |
|
| 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
|
|
|
|
