One shared queue, one listener and one monitor if the listener itself cannot fulfill that function. Listener's time out waiting on the queue and if they are not the last instance, close down. After a listener process a request, it checks the queue depth and if there are more than a high water mark number of messages, it clones itself assuming the limit of clones has not been reached.
You can program this (I tend to do that as then I know what is happening), but I think that also MQ comes with some tools and configurations that can auto start clients if the queue is too large and so on. Those clients need to know to timeout and stop though, you don't want external processes killing jBASE processes. Jim From: [email protected] [mailto:[email protected]] On Behalf Of Mujtaba Khan Sent: Friday, April 16, 2010 2:14 PM To: [email protected] Subject: Re: T24 - MQ speed and efficiency Hi, I am not that expert in MQ but i know that you can distribute your load in different queues and listeners for details you can see IBM website and subject as "Best Practices" and if your your MQ cluster than Using remote QM will help you also -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
