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 » Disabling Round Robin at mq level

Post new topic  Reply to topic
 Disabling Round Robin at mq level « View previous topic :: View next topic » 
Author Message
koko
PostPosted: Wed Nov 30, 2005 4:53 pm    Post subject: Disabling Round Robin at mq level Reply with quote

Master

Joined: 26 Sep 2003
Posts: 206

I have a unique problem. This topic involves both mq and workflow. Since I am not getting proper response from workflow forum, I am posting my question here.

I have a scenario where there are three qmanagers QM1, QM2 an QM3. QM1 and QM2 are hosting workflow servers. QM3 is hosting Websphere Application Server ( client concentrator ). QM1 and QM2 have full repositories.

We dont have access to the application code ( Its IBM propreitery ) where WAS opens up queues on QM3.

Whats happening is when ever we try to interact with GUI on WAS, it is sending messages in a round robin fashion to QM1 and QM2. I dont want it to work that way. I would like WAS to send all the messages to QM1 only. I repeat here that at the top most application level we do not have access to change any options while talking to QM3.


Is there any trick I can use to let all the messages go to QM1 alone.
_________________
Thanks

Koko
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 30, 2005 5:05 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Put disable the queue on QM2.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Wed Nov 30, 2005 6:12 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Uncluster the queue on QM2.
-or-
Delete the queue on QM2.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
hopsala
PostPosted: Wed Nov 30, 2005 6:50 pm    Post subject: Reply with quote

Guardian

Joined: 24 Sep 2004
Posts: 960

If you wish to keep the queue in QM2 available for other purposes, and you have WMQ v6 you can set CLWLPRTY parm of said queue (or even CLWLRANK) to a lower priority.
You cannot, however, by any means other than creating two clusters, have WAS send only to QM1 while other appls on the cluster send to both QM1 and QM2 (this regarding the same queue, of course).

Btw, I don't know Workflow at all, but my guess is there's a better solution on that level, rather than the WMQ network level; A BIND_ON_OPEN parallel is bound to be somewhere.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 30, 2005 7:13 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

hopsala wrote:
Btw, I don't know Workflow at all, but my guess is there's a better solution on that level, rather than the WMQ network level; A BIND_ON_OPEN parallel is bound to be somewhere.


It's actually WAS that's opening the queue for output, not workflow, at least according to the first post.

So I'd guess that it's either something in Process Choreographer/Server, or it's JMS. If it's JMS, then there's definitely an option on the Queue Destination for setting BIND_NOT_FIXED or BIND_ON_OPEN (but you know that, I think...).

If it's PC/PS, then I'm pretty sure there's an option. But I don't remember for PC and I haven't seen PS.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Dec 01, 2005 2:29 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

If it is indeed WAS the easiest thing to do is change the JNDI to explicitly ask for the queue on QM1.

Instead of binding the JNDI to the queue name in standard fashion, specify the qmgr name:

queue://QM1/MY.CLUSTERED.QUEUE?myoption1=value&myoption2=value...

That should pretty much guarantee that you hit only the queue on QM1.
No change to the program, no change to MQ.

Enjoy
Back to top
View user's profile Send private message Send e-mail
koko
PostPosted: Thu Dec 01, 2005 10:06 am    Post subject: Reply with quote

Master

Joined: 26 Sep 2003
Posts: 206

Thanks a bunch for all your suggestions.

QM1 and QM2 have to be in same cluster
QM2 and QM3 have to be in same cliuster

So QM2 cannot be unclustered.

The queue in question cannot be disabled as its a two way queue. Both WAS and Workflow use it.

Bottom Line I think I am screwed

I will open a ticket with IBM and try to post a solution once I find it.
_________________
Thanks

Koko
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Thu Dec 01, 2005 4:43 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722



QM1 and QM2 are in CLUSTERA?
QM2 and QM3 are in CLUSTERB?
so QM2 is in both CLUSTER1 and CLUSTER2?

Or are QM1, QM2 and QM3 in the same cluster?
_________________
Peter Potkay
Keep Calm and MQ On
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 » Disabling Round Robin at mq level
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.