| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message persistance |
« View previous topic :: View next topic » |
| Author |
Message
|
| techno_freak |
 Posted: Thu Dec 16, 2010 11:13 pm Post subject: Message persistance |
 |
|
Novice
Joined: 23 Nov 2010
Posts: 12
|
If persistence is specified by the MQSeries administrator in the MQSeries queue definition:
----------All messages placed on that queue will be treated as persistent, even those where persistence is not needed. This represents an unnecessary performance overhead.
If persistence is not specified by the MQSeries administrator in the MQSeries queue definition:
----------All essages will be treated as non-persistent, even those where persistence is needed. This represents an integrity exposure because non-persistent messages may be lost in the event of a system failure.
Question here is .. If application team set message to be persistence and Admin set Qs defpsist parameter to "NO". Whose(App or Admin) permission will take precedence. Can we choose to take precdence for permission. |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Thu Dec 16, 2010 11:19 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
in the application program you can set 3 attributes for persistence:
1. persitent - the message will be created persitent
2. non persistent - the message will be created non persistent
3. persistent as queue def - now (and only now) it depends on the persistence attribute of the queue.
once either persitent or non persistent is assigned to a message by one of these 3 methods, it will not be change by mq, no matter where the message is going or which queues it will hit. it can only be changed by getting and putting the message again.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| skoobee |
| Posted: Thu Dec 16, 2010 11:37 pm Post subject: |
|
|
Acolyte
Joined: 26 Nov 2010
Posts: 52
|
The DEFPSIST attribute of a queue is a default. SImilarly, the initial value of the persistence of a msg, MD.Persistence, is set to MQPER_PERSISTENCE_AS_Q_DEF.
If the app programmer does not change the MD.Persistence, the persistence of the msg wil be what the administrator has decided.
However, the programmer can decide to set the persistence himself, by setting MD.Persistence to MQPER_PERSISTENT or to MQPER_NOT_PERSISTENT, and this overrides any default set by the administrator. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Dec 17, 2010 4:55 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The persistence attribute of a queue is NOT a default; rather, it is an initial value. The programmer must specify one of these:
. This message is persistent; or
. This message is non-persistent; or
. This message should take on the persistence value set at the _as_q_def attribute.
_________________
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 |
|
|
| Vitor |
| Posted: Fri Dec 17, 2010 5:39 am Post subject: Re: Message persistance |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| techno_freak wrote: |
If persistence is specified by the MQSeries administrator in the MQSeries queue definition:
----------All messages placed on that queue will be treated as persistent, even those where persistence is not needed. This represents an unnecessary performance overhead. |
No they won't be.
| techno_freak wrote: |
If persistence is not specified by the MQSeries administrator in the MQSeries queue definition:
----------All essages will be treated as non-persistent, even those where persistence is needed. This represents an integrity exposure because non-persistent messages may be lost in the event of a system failure. |
No they won't be.
| techno_freak wrote: |
| Question here is .. If application team set message to be persistence and Admin set Qs defpsist parameter to "NO". Whose(App or Admin) permission will take precedence. |
Message persistence is (obviously enough) a message attribute and is always decided by the application putting the message. The application can choose to use the queue's initial value, or not.
| techno_freak wrote: |
| Can we choose to take precdence for permission. |
No. This behaviour is fixed. Message persistence can't be overriden by the administrator, and there are many, many discussions in this forum on the benefits & disadvantages of this.
<plug>3rd party software from Cressida can enforce message standards as shown here</plug>
I am not now nor have I ever been a Cressida employee, no warranty express or implied is offered on the generalised advice nor the suitibility or not of this software to your situation or requirements, etc, etc, etc...
In short; I'm just sayin'!!!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| techno_freak |
| Posted: Sun Dec 19, 2010 6:40 pm Post subject: |
|
|
Novice
Joined: 23 Nov 2010
Posts: 12
|
Thanks to a lot you for clarifying my doubt.  |
|
| 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
|
|
|
|
