| Author |
Message
|
| Trainee |
 Posted: Tue Apr 17, 2007 6:37 am Post subject: QueueManager Stopping and Starting Problem |
 |
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
Hi ,
Every time we need we stop Queue Managers with -i (immediate) option in our organization.Later IBM suggested that without -i is good and we try to do it on production while doing migration.
In one incident While stopping the queue manager associated with Broker without -i option it took nearerly 15 minutes and still Quiescing(Offcourese I stopped the Broker already).So then I killed the processes associted with the queue manager and it got ended abnoramally. Does this really harm the queue manager. This queue manager is in cluster also and complined about the cluster sender channel stopped abnormally.
We have 'q' program to move the messages from one Queue to Other Queue on the same queue manager and it is beaing called every15 minutes(crontab entry).
My questions are
1) Stopping the queue manger by killing the processes running againest to it leads any problem.Is there any process which should not kill at all something like that
2) As we have 'q' program to move the messages ..Do I need to stop that q program before stopping the queue manager?
3) Abnormal shout down indicates some thing wrong with the queue manager?
4) Do I need to Suspend the Queue Manager from the cluster as it complined ClusterSender channel got stopped abnormally when I try to stop it..?Queue Manager in cluster will take more time to get it stopped
5) What will happen to the messages in the message flows when I stop the Broker and then Stop the Queue Manager with -i option
Please advice...through some light on it
Thank you
Trainee |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Apr 17, 2007 6:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd say you have applications that aren't using FAIL_IF_QUIESCE.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Apr 17, 2007 7:28 am Post subject: |
|
|
Guest
|
| Look at the 'q' program source code. Does the program do an MQGET with wait option? I'd guess that the waitinterval is set for 15 minutes. MQGET with wait is an active MQ call. The -c and -i quiesce options allow active MQ calls to complete. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Apr 17, 2007 6:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
And make sure to SUSPEND the qmgr from the cluster before shutdown.
This effectively redirects all traffic that CAN be load balanced in the cluster to another qmgr in the cluster. This will help by lessening the traffic on the qmgr about to shut donw...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Trainee |
| Posted: Wed Apr 18, 2007 6:04 am Post subject: |
|
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
Thanks alot
1.Can I kill the process which are running againest a queue manager
2.What will happen to the messages in the message flows when I stop the Broker and then Stop the Queue Manager with -i option
3. Does Abnormal shout down indicates some thing wrong with the queue manager?
Thank you
Trainee |
|
| Back to top |
|
|
|
|
