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 » Queue Manager is not getting Stopped

Post new topic  Reply to topic
 Queue Manager is not getting Stopped « View previous topic :: View next topic » 
Author Message
amitk22784
PostPosted: Tue Dec 29, 2009 10:25 pm    Post subject: Queue Manager is not getting Stopped Reply with quote

Newbie

Joined: 23 Nov 2009
Posts: 9

Hi all

I am not able to stop Queue manager using endmqm command. The command is executed but it gives me this message

"Quiesce request accepted. The queue manager will stop when all outstanding work is complete "

but it does not stop the Queue manager. when i use dspmq command, it gives me following status


QMNAME(test1) STATUS(Quiescing)
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Tue Dec 29, 2009 11:21 pm    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

are there any applications / utilities active that do not honor the queuemanager shutdown request? if they stay active, and you shut down the qmgr mode quiesce, the queuemanager will not end unless those applications disconnect.

in addition, there are options of the endmqm command that help you in this situation. check the administration manual for those options.
_________________
Regards, Butcher
Back to top
View user's profile Send private message
zpat
PostPosted: Wed Dec 30, 2009 1:15 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Unless applications issue the FAIL_IF_QUIESCING option on their MQI calls - they are not notified of the queue manager quiesce condition.
Back to top
View user's profile Send private message
nathanw
PostPosted: Wed Dec 30, 2009 1:23 am    Post subject: Reply with quote

Knight

Joined: 14 Jul 2004
Posts: 550

which basically means that the QM will continue to take on new units of work i believe and therefore not shutdown.

if this is an urgent matter and you need it shutdown for a reason then i would add the -i flag to your endmqm

Code:
endmqm -i QM


this will shut down the QM straightaway even if it is quiescing however, you run the risk of losing data that is being processed at that time if it is not persisent.
_________________
Who is General Failure and why is he reading my hard drive?

Artificial Intelligence stands no chance against Natural Stupidity.

Only the User Trace Speaks The Truth
Back to top
View user's profile Send private message MSN Messenger
mvic
PostPosted: Wed Dec 30, 2009 1:35 am    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

nathanw wrote:
Code:
endmqm -i QM


this will shut down the QM straightaway even if it is quiescing however, you run the risk of losing data that is being processed at that time if it is not persisent.

Ending / restarting the qmgr will discard ALL its non-persistent messages except any that were successfully added to a queue with attribute NPMCLASS(HIGH).
Back to top
View user's profile Send private message
nathanw
PostPosted: Wed Dec 30, 2009 1:37 am    Post subject: Reply with quote

Knight

Joined: 14 Jul 2004
Posts: 550

mvic wrote:
nathanw wrote:
Code:
endmqm -i QM


this will shut down the QM straightaway even if it is quiescing however, you run the risk of losing data that is being processed at that time if it is not persisent.

Ending / restarting the qmgr will discard ALL its non-persistent messages except any that were successfully added to a queue with attribute NPMCLASS(HIGH).


isnt that what i said apart froom the NPMCLASS part?
_________________
Who is General Failure and why is he reading my hard drive?

Artificial Intelligence stands no chance against Natural Stupidity.

Only the User Trace Speaks The Truth
Back to top
View user's profile Send private message MSN Messenger
PeterPotkay
PostPosted: Wed Dec 30, 2009 5:44 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

nathanw wrote:
which basically means that the QM will continue to take on new units of work i believe and therefore not shutdown.

if this is an urgent matter and you need it shutdown for a reason then i would add the -i flag to your endmqm

Code:
endmqm -i QM


this will shut down the QM straightaway even if it is quiescing however, you run the risk of losing data that is being processed at that time if it is not persisent.


What data would be lost with endmqm -i that would not be lost with just endmqm?
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
mvic
PostPosted: Wed Dec 30, 2009 7:34 am    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

nathanw wrote:
mvic wrote:
nathanw wrote:
you run the risk of losing data that is being processed at that time if it is not persisent.

Ending / restarting the qmgr will discard ALL its non-persistent messages except any that were successfully added to a queue with attribute NPMCLASS(HIGH).


isnt that what i said apart froom the NPMCLASS part?

Well no - you said by ending the qmgr you run the risk of losing NP messages being processed at that time. In fact you lose all NP messages. It's not so much a risk as a certainty.

Ah yes, except for any NP messages are on queues with NPMCLASS(HIGH). In that case they are not automatically discarded.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Dec 30, 2009 3:00 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Quote:
Ah yes, except for any NP messages are on queues with NPMCLASS(HIGH). In that case they are not automatically discarded.

NPMCLASS(HIGH) - This setting enables nonpersistent messages on this queue to be retained across a queue manager restart. Nonpersistent messages may still be lost in the event of a failure.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
nathanw
PostPosted: Mon Jan 04, 2010 1:24 am    Post subject: Reply with quote

Knight

Joined: 14 Jul 2004
Posts: 550

mvic wrote:
nathanw wrote:
mvic wrote:
nathanw wrote:
you run the risk of losing data that is being processed at that time if it is not persisent.

Ending / restarting the qmgr will discard ALL its non-persistent messages except any that were successfully added to a queue with attribute NPMCLASS(HIGH).


isnt that what i said apart froom the NPMCLASS part?

Well no - you said by ending the qmgr you run the risk of losing NP messages being processed at that time. In fact you lose all NP messages. It's not so much a risk as a certainty.

Ah yes, except for any NP messages are on queues with NPMCLASS(HIGH). In that case they are not automatically discarded.


I stand corrected apologies.
_________________
Who is General Failure and why is he reading my hard drive?

Artificial Intelligence stands no chance against Natural Stupidity.

Only the User Trace Speaks The Truth
Back to top
View user's profile Send private message MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Queue Manager is not getting Stopped
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.