ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » proper shutdown sequence for qm

Post new topic  Reply to topic
 proper shutdown sequence for qm « View previous topic :: View next topic » 
Author Message
WLeideckDC
PostPosted: Thu Dec 16, 2004 6:31 am    Post subject: proper shutdown sequence for qm Reply with quote

Novice

Joined: 25 Aug 2004
Posts: 21
Location: Ludwigshafen, Germany

Hello,

I'm searching for a proper shutdown sequence for a qm.
My idea is

0. stop application
1. end command server if any is running
2. end trigger monitor s if any are running
3. end listener
4. stop channel
5. end qm
6. kill processes if any already exist
7. clear shared memory

Are there any other opinions?

Thanks in advance
Wolfgang
Back to top
View user's profile Send private message
Nigelg
PostPosted: Thu Dec 16, 2004 12:23 pm    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

FReplace all that by a single command, endmqm -i QMGR.
Why do all that elaborate stuff?
0 The apps will stop with Q_MGR_QUIESCING
1 The command server the same
2 The trigger monitor the same
3 You do not need to end the listener, it can be left running without a qmgr
4 Only do this if you want your channels to start up in STOPPED state, which means that you have to start them manually
5 JUST THIS ONE
6 What could be left?
7 Not necessary if the qmgr ended cleanly. Why do people think that this has to be done? The only time it may be needed is if the qmgr crashed, and it will not restart with AMQ8101, processes still running.
Back to top
View user's profile Send private message
EddieA
PostPosted: Thu Dec 16, 2004 1:40 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Quote:
The apps will stop with Q_MGR_QUIESCING

Assuming that they've been written this way.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
vennela
PostPosted: Thu Dec 16, 2004 2:32 pm    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

You can't end a listener if the QMGR is running (using endmqlsr ) . You have to end the QMGR before ending the listener
Back to top
View user's profile Send private message Send e-mail Visit poster's website
fjb_saper
PostPosted: Thu Dec 16, 2004 3:36 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

WLeideckDC wrote:
0. stop application
1. end command server if any is running
2. end trigger monitor s if any are running
3. end listener
4. stop channel
5. end qm
6. kill processes if any already exist
7. clear shared memory

Are there any other opinions?


Assuming you are also running WebSphere WAS this would be the sequence:
0 Stop WebSphere and all applications that connect in bindings mode
1 End command server
2 End qmgr (stops trm, chi, chl)
3 End listener
4 Kill processes if still exist (mainly due to apps in bindings mode that did not shut down)
5) clear memory (amqiclen)

Enjoy
Back to top
View user's profile Send private message Send e-mail
WannaBeInAParker
PostPosted: Thu Dec 16, 2004 7:36 pm    Post subject: Reply with quote

Voyager

Joined: 09 Dec 2003
Posts: 81

My $.02

Not knowing the circumstances, you may want to stop the channel before the trigger monitor as you may want to ensure that the application queues are drained.

Also, Q_MGR_QUIESCING should be used, in my experience bad assumption that it is.

Lastly, if it is the only queue manager running on the server and OS is Unix/Linux, you may want to clear shared memory. Just in case apps did not use Q_MGR_QUIESCING, you blow them out of the water and they will not effect restart (spoken like a true admin).
_________________
-WannaBe-
Back to top
View user's profile Send private message
WLeideckDC
PostPosted: Fri Dec 17, 2004 12:57 am    Post subject: Reply with quote

Novice

Joined: 25 Aug 2004
Posts: 21
Location: Ludwigshafen, Germany

I need this information because the QM is running in a serviceguard
environment and there is lot of traffic on the channels between applications that are on another servers. In case of a failover the package must switch
and sometimes the QM must hard stopped.
Back to top
View user's profile Send private message
WannaBeInAParker
PostPosted: Fri Dec 17, 2004 4:24 am    Post subject: Reply with quote

Voyager

Joined: 09 Dec 2003
Posts: 81

Also, you may want the application stopped after the trigger monitor (if its triggered), so you do not trigger again.
_________________
-WannaBe-
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » proper shutdown sequence for qm
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.