| Author |
Message
|
| sijtom0703 |
 Posted: Tue Jan 03, 2012 4:54 pm Post subject: messages are lost from a cluster queue manager on restart |
 |
|
Voyager
Joined: 28 May 2011
Posts: 84
Location: USA
|
I find the messages are lost from a cluster queue when I restart that cluster queue manager where the cluster queue is defined. I have not made the messages persistent in that queue.
But I was just thinking since it is a cluster queue and is published across all other queue managers in the cluster the messages should remain as long as the cluster remains active. Am I correct?? |
|
| Back to top |
|
 |
| mvic |
| Posted: Tue Jan 03, 2012 5:16 pm Post subject: Re: messages are lost from a cluster queue manager on restar |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
The most reliable way to make your messages persist across a queue manager restart, is to make them persistent.
Or, you might be able to use the NPMCLASS(HIGH) queue attribute. Check out the details in the MQ Information Center. |
|
| Back to top |
|
|
| ipmqadm |
| Posted: Tue Jan 03, 2012 7:32 pm Post subject: |
|
|
Acolyte
Joined: 18 Apr 2007
Posts: 68
|
The only way to ensure that the data remains in the cluster queue is to make that data persistent. You can either have the application that 'puts' the data in the queue make that data persistent, or as an admin you can define the local queue to be persistent.
The fact that the data is in a cluster is irrelevant... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 03, 2012 9:06 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ipmqadm wrote: |
| or as an admin you can define the local queue to be persistent. |
The admin setting is nearly irrelevant. What really matters is the application setting as it overrides the admin setting any time. The admin setting only comes into play when the app uses "persistence as qdef", and this can be altered by using alias or remote queues with a different setting..., so your choice of setting the persistence of messages should really be the sending app.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jan 04, 2012 1:20 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| ipmqadm wrote: |
| or as an admin you can define the local queue to be persistent. |
The admin setting is nearly irrelevant. What really matters is the application setting as it overrides the admin setting any time. The admin setting only comes into play when the app uses "persistence as qdef", and this can be altered by using alias or remote queues with a different setting..., so your choice of setting the persistence of messages should really be the sending app.
Have fun |
And if the messages originate from a remote queue manager, the QLOCAL setting will be totally irrelevant if the messages have been created non-persistent.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 04, 2012 5:30 am Post subject: Re: messages are lost from a cluster queue manager on restar |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sijtom0703 wrote: |
| I have not made the messages persistent in that queue. |
Non-persistent messages are never guaranteed to be retained. Clustering has nothing to do with this.
| sijtom0703 wrote: |
| I was just thinking since it is a cluster queue and is published across all other queue managers in the cluster the messages should remain as long as the cluster remains active. Am I correct?? |
You are not correct and I'd dispute "thinkiing". What exactly led you to "think" messages addressed to a queue that participates in a cluster goes to more than one instance of the queue in a cluster?
Publishing a message does not relate to a WMQ cluster except in that a WMQ cluster is a viable way of supporting the message transport of a pub/sub model. But they remain 2 spearate concepts.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sijtom0703 |
| Posted: Wed Jan 04, 2012 10:06 am Post subject: |
|
|
Voyager
Joined: 28 May 2011
Posts: 84
Location: USA
|
Thanks All for clearing me
| Quote: |
| You are not correct and I'd dispute "thinkiing". What exactly led you to "think" messages addressed to a queue that participates in a cluster goes to more than one instance of the queue in a cluster? |
My thinking was since the queue is a cluster queue and since this queue is accessible from all Queue Managers in the cluster it might be possible each cluster queue manager keeps a copy of this queue and since I did not restart the other cluster queue managers the messages should remain whether it is persistent or not !!  |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 04, 2012 10:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sijtom0703 wrote: |
| since this queue is accessible from all Queue Managers in the cluster |
No it isn't. It's a target for any queue manager in the cluster, but is only accessable from it's hosting queue manager.
| sijtom0703 wrote: |
| each cluster queue manager keeps a copy of this queue |
No they don't. They each have an instance of the queue, which is their own instance and not a copy of anything.
You need to spend a lot less time thinking and much more time reading the cluster documentation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
