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 » General IBM MQ Support » Cluster behavior

Post new topic  Reply to topic
 Cluster behavior « View previous topic :: View next topic » 
Author Message
girish_tharwani
PostPosted: Thu Sep 05, 2002 7:10 am    Post subject: Cluster behavior Reply with quote

Voyager

Joined: 01 Aug 2001
Posts: 88
Location: Pune, India

I have three queue managers (say QM1, QM2 and QM3) in a cluster. QM1 and QM2 both have a local queue each with same name (say LQ) that are shared in the cluster. So two LQ are visible on QM3. An application, that is connected to QM3, is trying to put a message on LQ. What happens if either QM1 or QM2 is down? Does MQ series takes care of sending all the messages put by app to the other queue manager? Does the binding option (Bind on Open or Bind on Put) make any difference in this situation ?

Thanks In Advance.
Back to top
View user's profile Send private message
bduncan
PostPosted: Thu Sep 05, 2002 2:33 pm    Post subject: Reply with quote

Padawan

Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley

You might want to use the search tool to look at past discussions on this subject - it's been quite a common one. Basically, what happens if QM1 or QM2 is down depends on whether you used "bind on open" versus "bind not fixed". Bind on open instructs the application to bind to a specific instance of the clustered queue when the MQOPEN is issued, and stick with this particular instance forever. So all subsequent MQPUTs will go to this one instance of the queue. If that instance becomes unavailable for some reason, the messages destined for it will start piling up on the SYSTEM.CLUSTER.TRANSMIT.QUEUE - they won't be rerouted to the other instance. On the other hand, if you use bind not fixed, every MQPUT will go to a different instance of the queue (round-robin style) and if one instance becomes unavailable, subsequent puts will go to whatever instances are still available. If all instances are unavailable, then you're up a creek. But again, take a look at some of the more in depth discussions on this site...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
Back to top
View user's profile Send private message Visit poster's website AIM Address
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Cluster behavior
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.