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 » decommission

Post new topic  Reply to topic
 decommission « View previous topic :: View next topic » 
Author Message
bujjisveeru
PostPosted: Tue Dec 15, 2009 9:56 pm    Post subject: decommission Reply with quote

Newbie

Joined: 08 Oct 2009
Posts: 3

HI,

There are many applications are connected with my application queue manager. But in one of those application is going to decommision soon. So if it happens, all the messages which are routing to the that application will hold in Transmission Queue (TQ) and if the TQ is reached maximum depth, then the messages are routed to DLQ(Dead-Letter-Queue). So it will effect the problem to remaining application also. Here is the main thing is: we hav only one channel for all the applications.
Back to top
View user's profile Send private message
Gaya3
PostPosted: Tue Dec 15, 2009 10:00 pm    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

it will be a problem....if the target is not going to be available..better find out a way to stop the messages going to that particualar queue.

The best option is stop the messages going to that target Q.

i believe the message will go to the Target Queue right, its not like going to stay in the Transmission Queue.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Dec 15, 2009 10:30 pm    Post subject: Reply with quote

Grand High Poobah

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

Gaya3 wrote:
it will be a problem....if the target is not going to be available..better find out a way to stop the messages going to that particualar queue.

The best option is stop the messages going to that target Q.

i believe the message will go to the Target Queue right, its not like going to stay in the Transmission Queue.

To avoid the channel MCA repeatedly retrying to put the message to a full queue (no app is processing them) and slowing down communications you can try following scenario:
  1. put inhibit the target queue on the processing qmgr
    This should let the channel MCA know to put the msg to the DLQ on the first try.
  2. run a DLQ handler that deletes the messages for that app until you can have them stopped at the source. This is to avoid the DLQ from just filling up.
  3. stop the messages at the source.

Now of course if you are just decommissioning the app and not the process , I would hope that you are replacing the app with another one. There the question arises if you can have the new app and the app to be decommissioned compete for message, for a short while. This would assure uninterrupted service...

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
bujjisveeru
PostPosted: Tue Dec 15, 2009 11:03 pm    Post subject: Reply with quote

Newbie

Joined: 08 Oct 2009
Posts: 3

suppose if it is in clustered environment, what to do?

tell me step-by-step
Back to top
View user's profile Send private message
Gaya3
PostPosted: Tue Dec 15, 2009 11:24 pm    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

who is the MQ Administrator there? Please get in touch with him/her
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Dec 16, 2009 6:08 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

bujjisveeru wrote:
suppose if it is in clustered environment, what to do?


The same thing, but in a cluster.

bujjisveeru wrote:
tell me step-by-step


Depends on your cluster topology. The advice to speak to your local WMQ admin is the best.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Dec 16, 2009 6:13 am    Post subject: Reply with quote

Poobah

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

Quote:
...all the messages which are routing to the that application will hold in Transmission Queue (TQ) and if the TQ is reached maximum depth, then the messages are routed to DLQ(Dead-Letter-Queue).

No. When the transmission queue reaches maxdepth, the next attempt to put a msg to the xmitq will result in the application getting a queue-full ReasonCode.

Part of the process to decommission an app is to modify the QRemote definition that the app MQOPENed to cause the messages to go somewhere other than the current xmit queue.
_________________
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
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » decommission
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.