ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » CLWLPRTY and the dead letter queue

Post new topic  Reply to topic
 CLWLPRTY and the dead letter queue « View previous topic :: View next topic » 
Author Message
jhidalgo
PostPosted: Tue May 27, 2008 12:08 pm    Post subject: CLWLPRTY and the dead letter queue Reply with quote

Disciple

Joined: 26 Mar 2008
Posts: 161

Hi mqas,

I want to know if someone has experienced the following, or knows if that happens.

Having a cluster with 3 qmgrs, two will have the same local queue shared in the cluster, lets call it REQUEST, so you use CLWLPRTY in the CLUSRCVRs so you can control the traffic, going to qmgr 1 or 2.

Lets say you have the qmgr 1 with its CLUSRCVR's priority in 6, and #2 with priority in 5, so all the messages will go to #1, BUT if the queue reaches its maxdepth then it will start queueing in the dead letter queue.

Will it send messages to #2 (without changing it's priority) ?

If I change the priority to a higher value on #2 all the messages will flow there, but is that the ONLY condition for that to happen ?

rgds
Back to top
View user's profile Send private message
bruce2359
PostPosted: Tue May 27, 2008 12:49 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Quote:
BUT if the queue reaches its maxdepth then it will start queueing in the dead letter queue.


(I will stop posting until my physician takes me off anti-inflamatories...)
_________________
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.


Last edited by bruce2359 on Wed May 28, 2008 6:52 am; edited 1 time in total
Back to top
View user's profile Send private message
jhidalgo
PostPosted: Tue May 27, 2008 1:28 pm    Post subject: Reply with quote

Disciple

Joined: 26 Mar 2008
Posts: 161

It seems like MQ doesn't look for the next destination if the priority is lower, that's the point.
Back to top
View user's profile Send private message
Nigelg
PostPosted: Tue May 27, 2008 1:39 pm    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

A destination queue full is not a reason not to send a msg to a qmgr. If the queue full causes the channel to go into RETRYING, possibly because there is no dead letter queue and persistent msgs are flowing, another qmgr is then chosen with a RUNNING or INACTIVE channel.
if the channel stays RUNNING because the msgs are put to the DLQ, then the msgs will continue to be sent there.
See the Clusters manual; CLWLPRTY has a lower priority in deciding a destination qmgr than the channel status.
_________________
MQSeries.net helps those who help themselves..
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Tue May 27, 2008 1:52 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzah.doc/qc10940_.htm

MQ does not consider the q depth, even its full and overflowing into the DLQ, when the cluster algorithm decides which q to put to. So the messages will still keep going to that q even if its full.

Of course you could code your own workload exit that checks the q depth of each clustered q before every put. You can guess how that will perform, right?

CLWLPRTY - it does its thing after checking channel status, so don't rely on this 100%. If the channel to your higher priority QM is anything other than Running or Inactive, it will choose the next QM. The channel will be something other than Inactive or Running as it goes from Inactive to Running.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
jhidalgo
PostPosted: Tue May 27, 2008 5:06 pm    Post subject: Reply with quote

Disciple

Joined: 26 Mar 2008
Posts: 161

Ok so the Queue Full event makes the channel to go into Pause, what I have seen is that the qmgr sending msgs will wait and there will be one new message in the destination's DLQ every 10 secs, after 50 messages all the flow will be redirected to the next qmgr with the next priority, BUT I am not able to identify the parameter(s) that is being used here.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » CLWLPRTY and the dead letter queue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.