| Author |
Message
|
| vinoth |
 Posted: Fri May 27, 2005 6:59 am Post subject: mesages in the persistent queue is missing after restart |
 |
|
Apprentice
Joined: 03 Mar 2005
Posts: 31
|
To my surprise i can find that the messages in the persistent queue is missing after the restart of the queu manager
Can anyone help me on this |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri May 27, 2005 7:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Persistance on a queue is a default value. That's why it's 'defpsist'.
An application can set the persistance of an individual message to anything it wants, and put it on any queue it wants. And if the message is non-persistant, it will not survive a restart (unless it's a non-persistant-that-can-survive-a-restart non-persistant message).
So everything is working correctly - except your applications (possibly!).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Fri May 27, 2005 7:25 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
| jefflowrey wrote: |
unless it's a non-persistant-that-can-survive-a-restart non-persistant message
|
 I like that phrase... Is that used also by IBM
But back to serious. Which messages would that be that are non persistent and would survive a restart?  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 27, 2005 7:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| sebastianhirt wrote: |
I like that phrase... Is that used also by IBM
But back to serious. Which messages would that be that are non persistent and would survive a restart? |
It's a new class of non-persistant message as of CSD8, I think.
I didn't want to look it up, so I used that pile of tongue tangling, but now I'll look it up.
Okay. It's a new attribute on queues -
| FixPack 10 Readme wrote: |
o New Queue Attribute
This WebSphere MQ V5.3 update introduces a new queue attribute
NPMCLASS which applies to local and model queues. NPMCLASS can
take one of two values:
1.NPMCLASS(NORMAL) - This is the default value and indicates
that non-persistent messages on this queue are only lost following
a failure, or a queue manager shutdown. These messages will be
discarded in the event of a queue manager restart.
2.NPMCLASS(HIGH) - This setting enables non-persistent messages on
this queue to be retained across a queue manager restart.
Non-persistent messages may still be lost in the event of a
failure.
|
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri May 27, 2005 7:41 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
Take a look at the NPMCLASS parameter on a queue:
| Code: |
NPMCLASS The level of reliability to be assigned to non-persistent messages that are put to the queue:
- NORMAL Non-persistent messages are lost after a failure, or queue manager shutdown. These messages are discarded on a queue manager restart.
- HIGH The queue manager attempts to retain non-persistent messages on this queue over a queue manager restart. |
|
|
| Back to top |
|
|
|
|
