MQSeries.net :: View topic

SSachdeva · Posted: Mon May 01, 2006 5:30 pm Post subject:

Hi all,
I wanted to see if you all had any ideas on how to solve this problem. I have 6 QMgrs - three are APP qmgrs and three are WBIMB Qmgrs all in the same cluster. This is in such a way to provide High Availability. We are using WMQ and WBIMB 6.0. I am running a publish/subscribe flow on the brokers and all the brokers are in a collective. The apps are using JMS Topic Connection Factories to publish and subscribe. The intention is that the app can publish from any APP queue manager to a STREAM queue on any of WBIMB queue Mgrs (since that queue is a cluster queue). If anyone of the broker qmgrs fail - the clustering should take care of routing my messages to another broker. What we are seeing though is that when a subscriber on the app qmgr registers a subscribtion - it works fine, but when it goes to deregister it does not really do so cause the deregister message could really go to any one of the three Broker QMgrs - not necc. the one it registered with. I understand that this is an unorthodox way of doing things (Using HACMP is out of the question) - but do you guys know of any way I can overcome this problem without loosing the psuedo HA I am getting from using Clustering. Im sorry if I have not explained this well - if so please ask specific questions and i will try an answer them to the best of my knowledge. Just to let you know currently the only viable option we can think of is setting an expiry for the register messages of the subscriber. But how is Pub/Sub reccommended to work in a Clustered Environment?

Thanks in advance.