|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Queue manager maintenance |
« View previous topic :: View next topic » |
Author |
Message
|
chris boehnke |
Posted: Mon Oct 26, 2009 2:08 pm Post subject: Queue manager maintenance |
|
|
 Partisan
Joined: 25 Jul 2006 Posts: 369
|
Guys,
We have MQ queue manager QM1(Prod environment) on solaris server and we are planning to apply MQ v6.0.2.6 patch.
This queue manager QM1 is in non-clusterted environment.
We have application AP1 connected to this queue manager QM1 for both input and output operations.
Before applying the MQ patch on server (where QM1 is running), I would first shut down the application and then shutdown the queue manager.
After shutting down the application AP1and before we shutdown the Queue manager, If we have messages arriving on to the queues(QM1) from remote queue managers(on different servers), and if they are non-persistant, they would be lost once we shut the queue manager.
Can you please suggest me how to avoid loss of messages ? |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Oct 26, 2009 3:18 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9472 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
f they are non-persistant, they would be lost once we shut the queue manager. |
This is the documented behavior of WMQ - non-persistent messages are summarily discarded at qmgr restart.
V6 and V7 have a queue attribute NPNCLASS. If set to NPMCLASS(HIGH), your non-persistent messages will be retained in the queue IF the qmgr ends gracefully. _________________ 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 |
|
 |
PeterPotkay |
Posted: Mon Oct 26, 2009 3:20 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
A. Set NPMCLASS to HIGH on your local queues and hope it works?
B. Tell the sender to stop sending them?
C. Stop your RCVR channels before you stop your consuming app?
D. Not worry about since if the app made them non persistent, they are OK with the messages going away in this scenario? What would the app do if the QM went down right now due to an unplanned outage?
(I would do C.) _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
Vitor |
Posted: Mon Oct 26, 2009 5:14 pm Post subject: Re: Queue manager maintenance |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
chris boehnke wrote: |
If we have messages arriving on to the queues(QM1) from remote queue managers(on different servers), and if they are non-persistant, they would be lost once we shut the queue manager.
Can you please suggest me how to avoid loss of messages ? |
By definition, it's acceptable to lose non-persistent messages. If the application design required the messages to survive queue manager restart (be it scheduled like this example or a crash from power failure) then they would have been set as persistent. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|