| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Messages are lost |
« View previous topic :: View next topic » |
| Author |
Message
|
| Gert |
 Posted: Mon Jun 18, 2007 2:59 am Post subject: |
 |
|
Newbie
Joined: 13 Jun 2007
Posts: 9
|
| Nigelg wrote: |
Why did you not do as I suggested?
Setting the NPMSPEED attribute to NORMAL causes non-persistent msgs to act like persistent msgs as far as channels are concerned, i.e. the msgs are read from the xmitq in syncpoint, and rolled back to the xmitq in the event of a channel failure. |
I will test it later on. I will keep you informed. |
|
| Back to top |
|
 |
| jsware |
| Posted: Wed Jun 20, 2007 12:04 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| Nigelg wrote: |
| Setting the NPMSPEED attribute to NORMAL causes non-persistent msgs to act like persistent msgs as far as channels are concerned, i.e. the msgs are read from the xmitq in syncpoint, and rolled back to the xmitq in the event of a channel failure. |
Bear in mind that this will not protect your messages in the event of a queue manager restart, only in the vent of a channel failure.
This may be OK in your design, it may be not.
PS. I think you can configure your environment with later versions of MQ to preserve non-persistent messages during a "normal" shutdown of the qmgr, but then they won't survive a qmgr/machine crash where the qmgr does not get shutdown "normally". The method of doing this escapes me at the moment. I am sure it is buried in the manuals somewhere.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| Gert |
| Posted: Wed Jun 20, 2007 1:43 am Post subject: |
|
|
Newbie
Joined: 13 Jun 2007
Posts: 9
|
| scottj2512 wrote: |
| Nigelg wrote: |
| Setting the NPMSPEED attribute to NORMAL causes non-persistent msgs to act like persistent msgs as far as channels are concerned, i.e. the msgs are read from the xmitq in syncpoint, and rolled back to the xmitq in the event of a channel failure. |
Bear in mind that this will not protect your messages in the event of a queue manager restart, only in the vent of a channel failure.
This may be OK in your design, it may be not.
PS. I think you can configure your environment with later versions of MQ to preserve non-persistent messages during a "normal" shutdown of the qmgr, but then they won't survive a qmgr/machine crash where the qmgr does not get shutdown "normally". The method of doing this escapes me at the moment. I am sure it is buried in the manuals somewhere. |
OK... then I will work with Persistent messages. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Jun 20, 2007 5:32 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
Scott - The parm you're thinking of is NPMCLASS. It's set per queue and only available on the distributed platforms.
Cheers
Steve |
|
| Back to top |
|
|
| jsware |
| Posted: Thu Jun 21, 2007 8:21 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| Toronto_MQ wrote: |
| Scott - The parm you're thinking of is NPMCLASS. It's set per queue and only available on the distributed platforms. |
I new it was in there somewhere. Looked all through the ALTER QMGR command and couldn't see it. 
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
