| Author |
Message
|
| masteringmq |
 Posted: Mon Dec 22, 2008 9:48 pm Post subject: NPMSPEED |
 |
|
Master
Joined: 20 Oct 2008
Posts: 200
|
| I realize that messages are building up in my transmission queue but discovered that there is no processing problem. Therefore this leads to a an explanation that the channel is not processing the messages fast enough. Therefore I set the NPMSPEED attribute of the channel to FAST. This applies only for non persistant messages. Are there possibilities to deliver persistant messages quickly?. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Dec 22, 2008 9:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Dec 24, 2008 4:51 am Post subject: Re: NPMSPEED |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| masteringmq wrote: |
| Therefore this leads to a an explanation that the channel is not processing the messages fast enough. Therefore I set the NPMSPEED attribute of the channel to FAST. |
NPMSPEED has nothing to do with how fast a channel moves a message. If the messages are not moving fast enough from QM1 to QM2, either the channel processes do not have enough CPU or memory, or more likely, your network bandwidth is to small for what you want to see.
NPMSPEED only deals with how non persistent messages are dealt with in regards to channel batches. Depending on your settings, that may appear to make the messages move faster, when in fact its only making them available that much faster on the receiving QM.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 24, 2008 6:48 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
NPMSPEED(FAST) means that the sending MCA will send non-persistent messages ahead of all other (persistent) messages, AND outside units of work.
If a non-persistent message is sent on a FAST channel, AND the receiving MCA cannot deliver the message to the destination queue and the dead-letter queue, you have directed the receiving MCA to discard the message.
Did you read the definition of NPMSPEED(FAST) in the WMQ Intercommunications manual before you made this change?
Can your applications tolerate this potential loss of messages?
_________________
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 |
|
|
| masteringmq |
| Posted: Wed Dec 24, 2008 5:13 pm Post subject: |
|
|
Master
Joined: 20 Oct 2008
Posts: 200
|
| Yes. Also if the channel terminates while the fast, non persistant message are in transit, the messages may be lost. Unless if my application can perform recovery. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Dec 26, 2008 5:32 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| bruce2359 wrote: |
NPMSPEED(FAST) means that the sending MCA will send non-persistent messages ahead of all other (persistent) messages, AND outside units of work.
|
It is my understanding that the messages are sent over in the same order that they are in the XMITQ. Its just that the non persistent ones are sent over a fast channel are sent outside of syncpoint, meaning they are available immediatly.
I searched and searched and was not able to find any doc confirming or contradicting this.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| gunter |
| Posted: Mon Jan 12, 2009 4:54 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
| PeterPotkay wrote: |
| It is my understanding that the messages are sent over in the same order that they are in the XMITQ. |
So do I, but with NPMSPEED(FAST) we had swapped non-persistent messages, we went back to NPMSPEED(NORMAL).
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
|
|
