MQSeries.net :: View topic - Clustered MQ with Clustered WAS MDB

MarkB · Posted: Mon Feb 06, 2012 9:41 am Post subject:

I was hoping someone could point me in the right direction concerning the configuration of WMQ and WAS when MDB's are used.

More specifically, what is the predominant approach to solving the problem of a clustered queue being routed messages when a consumer of those messages on a specific local queue has been disabled?

We have a clustered MQ v6 environment. All messages are put to a clustered queue name that is hosted on 2 queue managers. Each queue manager has a queue that has a WAS MDB listening or getting on it.

In the case where one MDB goes down (because of an unhandled poison message lets say), messages continue to be directed to both queue managers in the cluster, but are not being consumed off of one of the queues on one of the queue managers.

What is the recommended approach to solving this situation?

a) Reaching a reduced maximum queue depth on the local queue will result in messages being directed to the DLQ - not a great solution.
b) CCDT's only take effect at connect time, so it seems that this won't work with the MDB's that are always connected.
c) Using a cluster exit to monitor queue depth and "put disable" the local queue when a specific message depth threshold is reached sounds like a possibility, but the chances of shutting down a queue in the cluster when higher than expected volumes are encountered could be counter productive.
d) modifying the cluster message routing algorithm seems like a possibility, but is sort of heavy handed.

So, my question is, what have others done to manage this situation - what am i missing?

Thanks for reading this guys. Any info would be appreciated. If this is a silly question, please don't flame me. I've looked through the forum and could not locate a suitable solution.